is flash tricksy or....

[grand tarkin]

Just can't work this out : (

Check out the FLA, probably easiest, but please check * first.

I cant tell a movie clip on main timeline to gotoAndPlay(2);
It treats the command like a gotoAndStop(2); jobby!

Am i doing something really really stupid here?

* Is it possible for Flash to become corrupted and do weird stuff like this?
If so, what are the chances that this mess-up spreads to other precious FLAs?
Could this all have something to do with fluoridation of the water supply? (joke- first time ive smiled in hours)

If anyone can shed light on this i would be grateful.

[pellepiano]

Its strange. But if you move the movieclip to frame 4 it works

[grand tarkin]

I noticed that-
and if you put the gotoAndPlay(2); command in a sub-movie then it will work ok, unless (of course) you put that movie on a layer above the button_1 movie on the timeline (strangest of all?)

actually, i have to say that it is a huge relief that
1) i'm not doing something very silly to bring this on myself.
2) i'm not suffering from some kind of MX-induced cabin fever.

many thanx for relieving my fears on both these counts.

[sharey]

GT-

are you still having problems with this? I got it to work. Let me know if you still need the help

Josh -

[sharey]

GT-

are you still having problems with this? I got it to work. Let me know if you still need the help

Josh -

[monkeysquid]

grand tarkin, are you scottish by any chance? just wonering cos thats the first time i've ever heard the word "jobby" on the net.

[grand tarkin]

i got the thing to work sharey, but wondered what the hell the problem was? any ideas people?

[sharey]

Basically what I did, was went into your Button1 MC and I saw that the first 4 frames had a

_root.button_1.gotoAndPlay(2);
stop();

You dont need to repeat that code here, on frame 5 on the _root timeline there is an action that is already controling the button1 MC. It seems that the 2 identical bits of code are conflicting with each other. Now button1 MC will go to the second frame and play as soon as it hits the last frame on the _root.

Josh -

[grand tarkin]

if you take out that command within the button_1 movie and you can get the thing to work that way then this is an issue that affects some users but not others, cos it aint happening on two of my machines.
Oh well! Funny old life.

[sharey]

that IS goofy,
heres your file

Josh -

[ericlin]

When the player head goes, it needs to handle many scripts scattered in variaous sites including frame scripts and enterframe scripts. There is an order to perform them. If there are play() and stop(), then the order decides whether it should play or stop.

Frame scripts are performed from parent-to-children and front-to-behind. EnterFrame scripts are performed in reverse oder.

In summay, for frame scripts, the script in child will over-write the script in parent.

so, when the _root goes to frame5, it loads button1 mc and button1 mc starts at frame1 with those scripts. Your movie will be processed like this:

_root.button_1.gotoAndPlay(2);//_root script
_root.stop(); //_root script
_root.button_1.gotoAndPlay(2);//button1 script
_root.button_1.stop();//button1 script

The result is what you get. I think you know how to fix it.

[grand tarkin]

Cheers for the help on this.

At risk of repeating myself, if you take out the duplicated command within the button_1 movie then it still won't work.

Check out the new FLA below and see if you can get it to work.

Once again thanks for you help.