"gotoAndStop("sceneC", 1);"
Now once it gets to the 3rd scene, the rest of the navigation is set by coding the buttons individually. Each button has the following:
"on (release) blah blah blah
gotoAndStop(10);"
Here's the weird thing. When you click on that button, it actually goes to frame 11, not 10. I noticed it went a frame over, so I went back to the previous scene, removed the "gotoAndStop("sceneC", 1);" and retested the file. Same thing.
Now I changed the button to go to frame 9 (remember, I want it to go to frame 10 here), and when you click the button, it goes to scene 10. Weird.
So I put the gotoAndStop back in the keyframe, BUT i left out the ,1 part (which says to stop at frame 1 of that scene). Now when clicking on the button that is coded to go to frame 9, I expect it to go to frame 10 because of that glitch. But guess what happens, it actually goes to frame 9 now like it's coded to. So I put in frame 10 instead of 9, and WA-LA, it goes to frame 10 like I want it to. Can anyone explain?
Cliffs: If previous scene has gotoAndStop("scene" ,1);, buttons in next scene go over by 1 frame. If gotoAndStop code is removed, buttons in next scene go to proper frame.
