This content has been marked as final. Show 4 replies
I would just suggest not (EVER!) to use scenes, just make markers and (...)but not scenes cuz they're very hard to control, you might have alot of frames then but the scripting would be alot easier
robin1232 is correct, scenes and programming do not go together very well - this is because at compile the document is reduced to a single timeline which will affect any coding placed there and often have unexpected results. as for 'markers' - yes but let's use the term 'frame labels' and often are placed on a single layer of there own. The benefit of using labels is that you can navigate to a point in the timeline by the label name string, and if during development you wish to change the structure, you will not ahve to go back through all of you code based on frame 'numbers' and change them.
but to you problem - when are you attempting to execute this conditional statement? because if it is located on the first frame of the first scene in the main timeline, it will only execute once and from that point on never be called again. so you either need to place it within a method and call it regularly whenever the scene changes, or better yet change the structure of your document.
Thanks to both of you for your suggestions. I can consolidate it down to one timeline with labels, something I usually do. This project started out differently which i why i worked with scenes.
I consolidated the whole thing into one timeline and I still can't get the mute button to change in different sections based on what was done to it before.
I am still trying the code in my original post and it isn't doing anything.
** Edit, I'm going to change the way that the button is on the stage so that there is only one instance and it's placement will be controlled by AS using a tweener. Sorry for asking the above question.