On Jul 20, 2006, at 3:04 PM, Andy Dent wrote:
As I posted on a separate thread of its own a few days ago, stop
using msgbox for debugging this kind of thing.
I have done a lot of GUI and graphics programming and the LAST
thing you want is msgbox popping up and generating side-effects.
MsgBox still has its uses. Sometimes it's the fastest way to check
the order of events which is undocumented and different on various
platforms.
As long as one understands that the MsgBox is actually opening a new
window and how that relates to the app you are testing, one can use
them for many investigative purposes. There are also times where it
can get one into an endless loop.
For example, placing one in a Draw or Activate event will obviously
create an endless loop. But, as Andy mentioned, there are other
subtle actions that can also create a similar problem.
I have found that setting a timer to mode=1 is also effective as it
waits for the execution of other code before it runs its action
event. From that you can check properties set during the execution of
the code in question.
In no way does this replace better debugging procedures when errors
are generated.
Terry
_______________________________________________
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>
