At 10:18 AM -0600 2/24/06, Sean Arney wrote:
> 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.
What would remote debugging do differently and how would one use it to
make that situation easier to find?
The remote debugger, because it is running on a different machine,
doesn't cause activation/deactivation of the app you're debugging.
That's valuable in a situation like this, since activation and
deactivation themselves trigger paint events -- a case of the thing
you're trying to study being unduly affected by your method of
studying it. Remote debugging avoids that.
Best,
- Joe
--
Joseph J. Strout
[EMAIL PROTECTED]
_______________________________________________
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>
