I’m using flash 8 for Mac. I’ve been building an intermediate-level flash site for the design company I work for. I’m stumped by this seemingly simple problem: certain buttons on the site will direct the user to the wrong frame. This happens even though other buttons on the site use the identical actionscript, and those work fine.
I’ll just focus on one example. First to put it into context; the site has a large portfolio section with 10 categories, and each category having up to 12 sub-pages. Here’s a screenshot of how the portfolio section is divided up (the marks in blue are my own notes):
“intdesign”, “corp-id”, “printdesign” etc., are the main pages for each category. All the little labeled frames immediately after are the sub-level pages. They are given code names in a numbered sequence. So if we’re on “intdesign”, the 3rd level labels would be named int1, int2, int3 and so on. The screenshot above shows I’m currently looking at one of those sub-level pages which is labeled “int1”.
That’s just the context. Here’s the problem. The button circled at the bottom left has been given the actionscript written below.
[INDENT]on (release) {
gotoAndStop(“corp1”);
}
[/INDENT]
That’s it. Novice stuff, right? Once we release the button it should take me to “corp1” (frame 235). But instead, it actually takes me to “corp-id” (frame 234).
The same is true for every bottom left button found throughout the portfolio. They always send the playhead to the main page for that category, instead of the sub-level page specified. If the button said ‘gotoAndStop(“print4”);’ it would go to “printdesign” instead. If the button said ‘gotoAndStop(“dis12”);’ it would go to “display” instead. I just don’t get it.
I’ve checked for any conflicting goto frame actions, but I see none. I’ve also checked for duplicated label names, but found none. I tried fixing this by telling it to go to the fame number [gotoAndStop(235);] insted of a label, and it still behaves the same way.
This only seems to happen once my flash site is exported as SWF. If I try it when Frame Actions/Buttons are enabled in Flash, the buttons work fine.
If it only happens after export, is this a bug? Or am I overlooking something else?
