Extending Button Class?

1

Hi all, sorry if this has been answered somewhere else (I searched) or if the answer is super easy (It’s possible I’m just retarded).

I am working on an interface that will have literally hundreds of buttons, navigating back/forth/in-between dozens of sections and subsections. I love the ease of skinning/labeling the built-in button component, but my fingers are rebelling at the thought of typing(or at least copy/pasting) “on(release)/gotoandplay/lastSection=/etc”.

So, I figured since I was already planning on having extensive frame labeling, I would just make the instance name of the button the same as the frame label where I wanted it to go. Then just have “gotoAndPlay(this._name)” on each Button.

My question then is thus: How do i make the following a part of the button component (or a different version of it, so I still use the default component for the couple of buttons I don’t want to do this), everytime I drag one onto the stage?

on (click) {
	nextSection = this._name;
	lastSection = _root._currentframe;
	gotoAndPlay(nextSection);
}

Thanks so much to anyone who can help me out! And if there is a super easy way of doing this, please smack me, then let me know what it is :slight_smile:

2

Just in case anyone cares, I figured this out, thanks to the new help files included in 7.2. It was actually pretty easy, I just duplicated both the button component and button.as, renamed them and added the extra bits to my new .as. Now all I have to do is put my new button on the stage, change the label, icon and instance name and my fingers are very greatful. :krazy:

3

yeah thats breifly touched upon in the AS2.0 tutorial on kirupa. Sorry I didnt get here sooner or I could have told you without you having to look it up… though looking things up is always a good practice :stuck_out_tongue:

4

And pretty useless in this case before downloading 7.2, :smiley: the help files in the first release were sorely lacking (I thought) when it came to explaining how to extend components, especially for a class noob like myself. :beer:

5

Macromedia is definitely not known for their documentation :wink: … well that’s not entirely true since they are known for poor documentation :trout:

6

Indeed, I think if it weren’t for the Kirupa Krew (sorry… that was lame :sigh: ) I would have given up on Flash long ago. :stuck_out_tongue:

7

I haven’t had that much trouble with the flash documentation… then again I did go and get a flash book.
Truely bad documentation is found in the SWFKit helpfile. Barely any code snippets and the ones that are there use quotes like this: ``HI!’ '.