> I also found that using message boxes to indicate what part of the
> code I had gotten to, while irritating during normal program
> operation, is very handy to narrow down when the problem occurs. Then
> you stand a chance of being able to debug it properly using
> breakpoints and stepping instead of less handy ways.
I recomment against this suggestion in debugging any multithreaded code.
Putting a message box in such an application will just change things way
too much to represent anything similar to the original application.
However, in single-threaded apps, it won't cause any such issues, and
may be a good idea (if you remember to not include them in the retail
version, that is!).
-------------
Ehsan Akhgari
List Owner: [EMAIL PROTECTED]
[ Email: [EMAIL PROTECTED]; [EMAIL PROTECTED] ]
[ WWW: http://www.beginthread.com/Ehsan ]
Physician, heal thyself: then you will also heal your patient. Let it be
his best cure to see with his eyes the man who heals himself. -Thus
Spoke Zarathustra, F. W. Nietzsche
