If this code is on frame 1 and you allow your "prev" button to return back to that frame it will re-assign all the buttons again and again. You should definitely init your app on frame 1 but then disallow the app to return to frame 1. So push all your content over to frame 2+ and never return to frame 1.

Otherwise you can set a flag for yourself to know if you need to assign the button handlers. If it's the first time you run the app you can check for the existence of a variable. If it doesn't exist then set it and init your buttons.

e.g. Frame 1:

if (!applicationAlreadyStarted)

{

     // add event listeners

 

     var applicationAlreadyStarted:Boolean = true;

}

Then the next time it hits that frame the variable will exist and you won't accidently re-assign all your buttons. Add any other init code in there that should only fire off once when your app is started. It might be what's causing trouble.

In your case I think the second method I mentioned may just be easier for you so you don't need to affect the timeline. However I can't recommend that unless I know what your timeline looks like.

Before continuing can you tell me of the buttons "back_btn", "next_btn" and "menu_btn" exist across the entire timeline without any keyframes breaks between them? If so the layer would look solid, similar to this where you see different content keyframes on all 10 frames but the buttons layer has no keyframes past frame 1:

As you can see the buttons layer has one long gray keyframe. Therefore any code inserted in frame 1 will continue to exist on the buttons all the way up to frame 10.

However if you insert a keyframe on the buttons layer, flash will "re-create" those buttons. Therefore they will not have any code applied to them unless you specifically apply it yourself on that frame. An example of that looks like this:

That would require you to re-apply your mouse click listeners every single frame to assure they work.

This just a quick example not to be taken too literally but I need to know what your timeline looks like to make the best suggestion.

You can make it as simple as:

function backFunc(evt:MouseEvent):void

{

     if (this.currentFrame > 1)

     {

          prevFrame();

     }

}

If the frame isn't "greater than 1" then it will simply ignore the click. Use the same logic in nextFunc and see if you can write it so if this.currentFrame < 6 it will fire off nextFrame();.

Often you need to look inside code to see what's going on. That code looks fine to me. I re-wrote it but added some trace() statements. When you press your next_btn you should see the messages I'm trace()ing. See if anything unusual is happening.

function nextFunc(e:MouseEvent):void

{

    var invalidFrames:Array = new Array(5, 11);

    var validPress:Boolean = true;

   

    for (var i:int = 0; i < invalidFrames.length; i++)

    {

        trace('Checking if invalidFrame[' + invalidFrames[i] + '] == [' + this.currentFrame + ']');

        if (invalidFrames[i] == this.currentFrame)

        {

            trace('Invalid frame matched, press invalid');

            validPress = false;

            break;

        }

    }

   

    if (validPress)

    {

        trace('No invalid frame detected, running nextFrame()');

        nextFrame();

    }

}

Your trace output can be found in the output panel. Say you're on frame 11, you should see something like this:

Checking if invalidFrame[5] == [11]

Checking if invalidFrame[11] == [11]

Invalid frame matched, press invalid

If you were on frame 1 then it should look like:

Checking if invalidFrame[5] == [1]

Checking if invalidFrame[11] == [1]

No invalid frame detected, running nextFrame()

Use trace() statements as much as possible along with your debug panel to track down logic issues.

The code tends to be right. Might want to run your play head across the timeline and take a look at the frame number you think is wrong and I bet you'll see it's right. For example the menu you might think is appearing on frame 5 actually appears on frame 4, or vice versa.

Glad you got it working. If you're all set please mark it answered so we can attend unanswered questions and good luck!

You're welcome and please mark it answered so us forum hounds can filter out answered questions. Good luck!