Another gotoandplay problem

[nuggety]

Can someone help me figure out what I am doing wrong here? I have 3 different frames and two buttons. You start on frame "Health", and there are buttons that are supposed to take you to "Definitions" and "Chart." Here is my code:

this.btn_MedDef.addEventListener(MouseEvent.CLICK, goMedDef);
this.btn_MedChart.addEventListener(MouseEvent.CLICK, goMedChart);

function goMedDef(event:MouseEvent) {
    gotoAndPlay("health-def");
}
function goMedChart(event:MouseEvent) {
    gotoAndPlay("health-chart");
}

But what is happening is that when you click the button, it takes you to different frames each time you click. For example, you click the button to go to Definitions (btn_MedDef) and it does take you to that frame. But if you click it again, it takes you to Health. Click it again, and you're back at Definitions. The other button behaves the same way: click on "Chart" (btn_MedChart) and it takes you to Definitions. Another click takes you to the Chart. Another click takes you Definitions again.

Any idea why it is behaving this way and how to fix it? Thank you!!

[@]

Try changing it to gotoandstop();

[nuggety]

Try changing it to gotoandstop();

Thanks - I tried this and it did stop the problem of it changing with each click, but now both the buttons go to the wrong screens (Definitions goes to Health, Chart goes to Definitions). I've checked the frames and the labels all seem to be correct (i.e. the Definitions frame is indeed labeled "health-def"). What could be causing this?

[@]

try not using a - in the frame label. just use healthDef and healthChart

[nuggety]

try not using a - in the frame label. just use healthDef and healthChart

Still not working

The weird thing is that earlier in the presentation, I have the exact same thing - a screen with several buttons that go to different frames and it works just fine. I used the exact same code, just changed the button, function and frame names (I had dashes in the frame labels there too). I can't understand why it's working there but not here.

[@]

without seeing the source file, I really can't help you debugg this anymore than I have. There might be an issue with using the same instance of a button on the same layer, or you might be using scenes that are some how getting out of scope. if you can post up the source files, i will see if I can help you out more.