On Aug 30, 2005, at 11:43, Joseph J. Strout wrote:
I'm not sure what to suggest, except the obvious things: if it's
not painting correctly, try a breakpoint in Paint; if it doesn't
respond properly to clicks, try a breakpoint in MouseDown or
Action; and so on.
The problem, as you might guess from the other thread (pardon the
pun), is on quitting the program. And since I don't have any quit
code I don't have anywhere to put a breakpoint. So why is quit
different than clicking on the sole window's close button? And where
do I put a breakpoint to check?
But note that trying to use the debugger on UI issues (especially
the Paint event) can sometimes cause the problem to squirm around,
as deactivating your app to bring the debugger forward triggers
other events (Activate, Deactivate, Paint, etc.). So this may
itself change the behavior. In such cases, the best approach is to
either use logging instead (e.g. System.DebugPrint), or run your
app on another machine via remote debugging.
No idea how to do that ... I'll have to look into that. Covered well
in LR or UG?
-- Chip
_______________________________________________
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>
|