The danger with App.DoEvents is that you might trigger an event
which calls DoEvents which triggers an event which calls DoEvents,
potentially ad infinitum.
When we originally introduced DoEvents, it was also possible to
cause problems by running the event loop on more than one thread at
a time. We later changed the implementation such that calling
DoEvents from any other thread simply yields to the main thread, so
this is no longer a concern.
DoEvents is useful when you have a modal, non-reentrant process
which needs to update the GUI. It sounds like this is the original
poster's situation.
Hi Mars
That's great info to have. Makes total sense and makes it clear where
it's safe to consider DoEvents. I've always used it in that context
and never had any problems with it.
Thanks,
Joe
_______________________________________________
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>
