View comments | RSS feed

gotoAndPlay function

gotoAndPlay([scene:String], frame:Object) : Void

Sends the playhead to the specified frame in a scene and plays from that frame. If no scene is specified, the playhead goes to the specified frame in the current scene. You can use the scene parameter only on the root Timeline, not within Timelines for movie clips or other objects in the document.

Availability: ActionScript 1.0; Flash Player 2

Parameters

scene:String [optional] - A string specifying the name of the scene to which the playhead is sent.

frame:Object - A number representing the frame number, or a string representing the label of the frame, to which the playhead is sent.

Example

In the following example, a document has two scenes: sceneOne and sceneTwo. Scene one contains a frame label on Frame 10 called newFrame and two buttons, myBtn_btn and myOtherBtn_btn. This ActionScript is placed on Frame 1, Scene 1 of the main Timeline.

stop();
myBtn_btn.onRelease = function(){
 gotoAndPlay("newFrame");
};

myOtherBtn_btn.onRelease = function(){
 gotoAndPlay("sceneTwo", 1);
};

When the user clicks the buttons, the playhead moves to the specified location and continues playing.

See also

gotoAndPlay (MovieClip.gotoAndPlay method), nextFrame function, play function, prevFrame function


Version 8

Comments


No screen name said on Sep 14, 2005 at 8:50 PM :
The gotoAndPlay and gotoAndStop functions, using a variable or expression for the frame, will go to the WRONG FRAME if you use any scenes and do any rearranging of scene order.

Flash 8 (and all previous versions of Flash) generates incorrect action bytecodes when it compiles the script and the gotoAndPlay / gotoAndStop will go to a frame at an offset from the frame you specified ... even if you use frame labels.

It is best to avoid using the function form of gotoAndPlay and gotoAndStop .. always use the Movieclip method version instead, as this does not have the bug.
No screen name said on Jun 29, 2007 at 2:00 AM :
Is there any workaround to this bug?
I experienced it at a quite late stage and it is now extensive work for me to redo the work I have already done.
juankpro said on Aug 1, 2007 at 8:40 AM :
I ran into the same problem on Flash 4 a very long time ago. So sad the bug was not corrected. To correct it i had to create a new .FLA file, create the scenes in the correct order and then copy the frames on each scene on the original FLA file to the corrected FLA file. This corrects the bug.

 

RSS feed | Send me an e-mail when comments are added to this page | Comment Report

Current page: http://livedocs.adobe.com/flash/8/main/00001732.html