ActionScript Play Controls Malfunction

[bluephoenix]

Hey all...

I'm doing a presentation for work consisting of several photos, animations and sound clips. I've encapuslated the project so that it is made up of a series of movie clips (based on each sound clip).

My time line resembles:
[--------'----------'----------'-----------'------]
[actions][a|a|a|a|a|a|a|a|a|a|a|a|a|a|a|a|a|a]
[m_clips][o|o|o|o|o|o|o|o|o|o|o|o|o|o|o|o|o|o]

stop(); has been assigned to each action frame.

at the end of each movie clip I've assigned the actionscript:
stop();
_parent.play();

The idea is that the playhead moves to frame 1, stops while the first clip plays. Once the first clip is done playing it tells the main timeline to play again. The playhead moves to frame 2 but stops again to let the 2nd clip play. This goes on and on until all clips have played, ending the movie.

I've done this before and it's worked fine for me. However I seem to be running into a problem with my current project. The playhead moves and stops all the way up to, say, frame 9. The ninth movie clip plays... but then that's it.

I'm not sure where the hang up is, either clip 10 isn't playing, clip 9's not advancing the main playhead, or whatever else.

I've checked to see if there were some stray ActionScripting statements, but I didn't find any. And the function calls are the same. That is...

frame 9 [actions]: stop();
frame 10[actions]: stop();

movieclip9[last frame]: stop(); _parent.play();
movieclip10[last frame]: stop(); _parent.play();

Has anyone run into this problem before? Is there anything else that can interfere with ActionScript's play controls?

Thanks in advance,

-Tim

[CharlesFK]

i never ever use the play() function.

instead use _parent.gotoAndStop(_parent.currentframe + 1);

[bluephoenix]

Bah! never mind. I figured it out.

It's movie clips that play, not graphics. I must have been half alseep when I converted the initial objects to a movie clip.

... we don't have an embarassed emoticon available, do we?

-Tim

[solomatrix]

[bluephoenix]

Yeah, lol. I guess everyone's entitled to have a brain-fart once in a while.

I like the idea of _parent.gotoAndStop(_parent.currentframe + 1), but I'm curious if there's a particular reason you're not using the stop and play functions.

-Tim

[CharlesFK]

for some reason, the play() and stop() methods seems to have a higher priority than gotoAndPlay() and gotoAndStop() so if there's already a stop() in a timeline and you call gotoAndPlay(), the goto part will be executed but not the play part.