This content has been marked as final. Show 7 replies
What kind of script did you add? Sometimes Flash does that warning when it hasn't got any status messages/data for a certain period of time..
Thanks for replying!
Sorry for the delay...
I'm an old man and I was sick these days...
The script I added is very simple and clean: it loads arrays to populate a new ComboBox and a Listener to drive this ComboBox.
Nothing very special here.
The Movie contains 23 ComboBoxes with similar scripts.
All of the ComboBoxes are set invisible by default and some of them are called on demand depending the Frame in which we work.
Very simple... indeed!
Remark: despite the warning, if I DON'T abort the script everything is working fine and operations are flashy. The Movie becomes erratic if I abort the script and then nothing is working !!!!!
Problem is the warning doesn't indicate WHICH script is involved and it is annoying.
Using the Debugger is very complex for me and doesn't do an analysis of the Movie scripting...
that warning is usually the result of a for-loop or while-loop that's taking more than 15 seconds to execute. for example, looping more than 10,000 times may start to cause problems on some computers.
Thanks kglad for your reply.
Of course, the first things I verified were the for statements.
But everything was fine.
I finally found the mistake:
The code below wasn't in the first frame! it was in frame 10 of the main Timeline.
After I placed it in the first frame the movie worked nice.
I found the reason, but could you explain why a misplacing of this code has such consequences?
With your explanation, other users will have a well documented answer to this problem...
that code wouldn't cause a timeout problem.
Of course, the code itself wouldn't, but what about its position in the Timeline?
the code's position is not relevant to any timeout issue. something else is/was causing your problem.