|
Prev: About UpdateStage.com
Next: linked swf path
From: Darrel Hoffman on 5 May 2008 15:04 Okay, this one makes no sense at all. I found a bug that causes the projector to advance 1 frame, causing a large number of scripts to fail, because they're checking for the frameLabel. The weird part is the bug occurs ONLY in Projector mode, and not Authoring. What I can't figure out is why the frame is changing in the first place - there's no code anywhere telling it to do that. All frame-related code either says "go the frame" or it says to go to a specific marker, never "go the frame + 1" or "go next" or anything like that. The other weird thing is it always seems to be triggered by a right-click of the mouse. Anybody ever see anything like this before?
From: Darrel Hoffman on 7 May 2008 13:28 Okay, after a bit of error-checking, I've discovered that this is caused by the frame script NOT running sometimes, just for one frame. Thus, my script saying: on exitFrame go the frame end is simply not happening for one frame, and the movie naturally advances to the next frame. (The frame scripts are all stretched out to at least 5 frames, so the movie then holds on that next frame.) Now, WHY this script is not occurring when the right mouse button is clicked utterly baffles me. I've made a quick and ugly patch for the problem with the following code: if the frame mod 5 > 0 and the frame > 1 then go the frame - (the frame mod 5) This makes sure the frame always stays on a multiple of 5 (or frame 1, since there isn't a frame 0), and even if it advances 1 frame for unknown reasons, it will automatically jump back to the most recent multiple of 5. Since all my markers are set at multiples of 5, this corrects the problem, but it doesn't explain why the problem occurs in the first place. Also, this is only a partial solution, as the movie will still be sitting on the wrong frame for 1 frame - so far this doesn't cause any errors, but there's always the possibility that a complication could occur. Moreover, I don't think I should HAVE to fix the problem this way, the "go the frame" script by all rights SHOULD execute every frame, but for whatever reason it doesn't, and I'm forced to accomodate. Anybody have a clue what could be causing this?
|
Pages: 1 Prev: About UpdateStage.com Next: linked swf path |