CHALLENGE! Solved.

[Colin Moock]

flashershocker [dot] com

,Internet writes:

>Hi Dave,


> Frame Actions work the same as Button Actions except that they happen

>when you goto that frame, whether it is in a Movie Clip or on any main

>timeline in any movie loaded with Load Movie.  The only difference is

>there are no Mouse Events for frames. Follow Jim'a advice but do it in a

>Frame Action instead of a button Action and it WILL work. 


Actually it probably won't work, depending on how it's implemented.


Here's the problem:


Say we have a movie.

Call the main timeline "MAIN". 

Timeline "MAIN" has two scenes. 

Scene 1 runs until frame 50, then stops.

Scene 2 is runs a movie for 300 frames. The first frame is labeled

"start".

Now, suppose you embed a movie clip ("CLIP A")  in MAIN at scene 1,

frame 1.


Clip "A" has a "Goto And Play" with an action on frame 40 that targets

".." or "/" with "Goto And Play" scene label "start" (which should be

MAIN, Scene 2, Frame 1).


It looks like this:

MAIN: 0--10--20--30--40--50 (stop on frame 50)

CLIP: 0-10-20-30-40 (goto and play "start", target "/")


If you were to actually build this, you'd find that the "Goto and Play"

action actually gets interpreted only as "Goto". The movie won't play.

Here's why:

If CLIP A tells MAIN to "Goto and Play", MAIN will "Goto and Play" (not

just "Goto") the frame in question *only if* the layer containing CLIP

A actually extends to that frame. If the layer containing CLIP A runs

out of frames before the labeled destination frame, then the action

will only be a "Goto". I don't know why it works this way, but it does,

and that kind of sucks. I ran into it first in GWEN Episode 2.


Of course, when you're using Scenes, you can't just extend the frames

in the layer containing CLIP A. You have to insert another instance of

the clip because there's a keyframe in Frame 1 of Scene 2.


So, DG, I understand your frustration. Here are your workarounds:


1) You know you can at least make CLIP A send a "Goto" successfully to

the MAIN timeline in Scene 2. Since CLIP A can't tell MAIN to play,

make MAIN tell itself to play: put a "Play" action on the appropriate

keyframe in your MAIN timeline.


2) Don't use scenes. Set your CLIP to tell your MAIN to Goto and Play a

frame later in Scene 1, and make sure the frames in the layer which

contains CLIP A extends at least as far as the destination frame.


Here's what it looks like:

MAIN

LAYER 1: 0--10--20--30(start)--40--50--60...

LAYER 2: 0--10--20--30--40|

	-place clip on layer 2, frame 0

	-layer 2 must extend to frame 30


CLIP: 0--10--20*

*="goto and play, target /, label: start"



And for clarity, here's what would only produce a "Goto":

MAIN

LAYER 1: 0--10--20--30(start)--40--50--60...

LAYER 2: 0--10--20

	-place clip on layer 2, frame 0


CLIP: 0--10--20*

*="goto and play, target /, label: start"


(CLIP A will execute its action on Frame 20, but will only complete the

"Goto" portion because the clip layer doesn't extend to the destination

frame "start").



It's a bit of a mess, but you should be able to get something working

with that. I've already done the test movies to demonstrate the issue.

I'll post them later today so you can see it in action.


MM, is this a bug?


Colin

colinmoock.iceinc.com/gwen/


------------------------------------------------------------------------

To UNSUBSCRIBE send: unsubscribe flasher in the body of an

email to

list-managershocker [dot] com

.  Problems to:

ownershocker [dot] com

N.B. Email address must be the same as the one you used to subscribe.

For info on digest mode send: info flasher to

list-managershocker [dot] com