Anybody knowing flash can help me out with this...

I have done a series of plain animation without writing codes(mainly motion tweens and stuff like that). I finally arrive at 4 btns that I have created and also anmated them. The buttons are coming at the last part of the animation, viz., ~130th frame.

As far as I know, while writing a code for the animation, its recommended to open a new layer and write a code in it.

I want to change the alpha settings etc, when moused over. It can be only done with the script alongwith. All the 4 buttons stop at same frame. I have given them distinct kinda names in all sense(instance, layers, library).

Now,When I open a new layer and put in my code in there, the code is being implemented to the first frame of the whole animation only and not on the frame that I want to. No matter, how hard I try, I always can't make the Actions to come onto the frame that I want. And hence, what I write is not being implemented actually.

I know its being implemented to the first frame only, bcos, if I write a stop function, the animation stops itself at the first frame.

Now, I need to know, how to apply actions(code) to a particular frame only?

Note: I am using Actionscript 3.0

Dude i am not sure what your exact problem is, but if i get you right, you want to make your code work on the specific frame that your action is to occur and not on the first frame, well have you tried to remove the stop() script to allow the movie play along then maybe create another keyframe over the frame you want your specific action to occur and place in your scripts as well as the stop() script so that your movie does not loop again..... let me know how it goes

Oh! thanks in your interest but, I have already created the flash... Actually, I restarted the computer and re-opened the file and tried and it really worked!!! Seems strange, but you'll have to believe it! The flash file you see below(my signature) is itself what I was talking about...


Enjoy! mtrackerbeyond!

I also agree to this as I have also faced the same situation and has done the same above mentioned thing.

Oh! OK... May be it should be reported to Adobe soon! Thanks...

Topic resolved way long back in time... So,

Topic--->Closed