| 24/02/06 ~ 13:07 -0500 :
| [EMAIL PROTECTED],
| " Re: endless graphics loop "
> As for debugging, this sort of problem is best tackled with the
remote debugger. This will of course require two computers (ideally,
side by side). Another option is to forego the IDE's debugger and
> make liberal use of System.DebugLog instead.
To avoid adding external trouble (as mentioned by PhilM), I do not
use any external system and create some internal debugging and
logging system. The most convenient one is making another window
containing a listbox, and whatever code line is suspected is then
preceded by another line which adds a row in the listbox stuffed with
event name, incremental counter, timing, variable values or whatever
is relevant. This needs no debuglog dialoguing, no remote machine,
and can be highly personalised...
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
