Irv Kalb <[EMAIL PROTECTED]> wroot > As an aside, 99.999% of the time, using the debugger will not make > your code behave differently. It is just a tool that allows you to > analyze what is going on in your program. In the odd .001% of the > time, the use of the debugger somehow changes the environment.
One of the most obvious gotchas for using the debugger is if you are relying on mouse or keyboard states to be polled correctly while stepping through. Another would be related to time, timeouts and so on. If you have a quicktime movie running (direct-to-stage or not), entering the debugger will not stop the playback of the movie. Presumably this is true of other special visual member types such as flash or animated gifs, although I have not tried this. Certainly entering the debugger halts the playback head, so commands which set the properties of sprites will not be seen immediately unless you insert some 'updatestage' commands, which can have side-effects of their own, most significantly in that it calls 'prepareframe' on all the behaviors in the current frame. In none of these cases is the code behaving 'differently', it's just important to note that the context of debugging can affect the state of many objects in unexpected ways. -Brennan [To remove yourself from this list, or to change to digest mode, go to http://www.penworks.com/LUJ/lingo-l.cgi To post messages to the list, email [EMAIL PROTECTED] (Problems, email [EMAIL PROTECTED]) Lingo-L is for learning and helping with programming Lingo. Thanks!]
