About gotoAndStop function

Question

Hi Everyone,
This is Vinay. Hope you all are doing well.
I have a problem with my flash file. Can anyone tell me how
can I use gotoAndStop function. Actually I have a Movieclip on the
stage and inside that two buttons are there. What I want is if I
click on the buttons it should take me to the frame one of the
second scene. For this I used the below function on one of the
buttons.
on(press)
gotoAndStop("sceneTwo", 1);
But it is not working. Can anyone solve my problem?
Thanks,
Vinay

Answer 1

clbeech,
> I'd thought about suggesting _parent here though
although
> that also seems to only work 'sometimes' - and this must
be
> the reason why perhaps?
It gets even more complicated with the use of on() and
onClipEvent(),
because event handler scope changes between the attach
approaches and their
dot notation equivalents. Compare this (on a button symbol
directly in the
main timeline):
on(release) {
trace(this);
... which traces _level0, with this (same button, different
approach):
myButton.onRelease = function():Void {
trace(this);
... which traces _level0.myButton. Awesome, right? lol
> does any path indication other than local, force the
change to
> the MC method? (which would explain a lot lol)
I would have to study more to give you a definitive answer,
but my hunch
is that a lack of object reference -- that is, simply
gotoAndPlay(), or the
like -- results in the stand-alone function. In AS2, anyway.
It would
certainly result in the function (vs the method) if you
publish prior to
Flash Player 5.
In contrast, the presence of an object reference -- e.g.,
this.gotoAndPlay() or _parent.gotoAndPlay() -- results in the
method as a
matter of course. After all, you're invoking a MovieClip
method on a
MovieClip instance.
In AS3, you only get the method, because most of these
ambiguously
"gray" duos are gone. And AS3 re-introduces the scene
parameter. But I
just had a conversation with kglad in another thread in which
CS4 seems to
ignore the scene parameter, even in AS3. Unfortunately, I
haven't done more
testing there either. If it's a bug, then I'll do what I can
to file a
report with Adobe.
David Stiller
Adobe Community Expert
Dev blog,
http://www.quip.net/blog/
"Luck is the residue of good design."