On Nov 4, 2006, at 6:44 AM, Joe Huber wrote:
In my experience, and from what I've read of this controversy, App.DoEvents primarily causes problems when called from an asychronous event (eg socket or serial) or from an RB thread.
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.
Mars Saxman REAL Software _______________________________________________ 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>
