On Nov 4, 2006, at 1:45 PM, Mars Saxman wrote:
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.
Excellent information on the DoEvents "discussion" and also explains
why I've not run into the issues of concern - previously, I didn't
use threads and now I only use DoEvents in just such modal situations
(otherwise, the GUI updates normally anyway).
However, maybe there could be a discussion of possible methods which
would allow dylib creators to properly provide cycles back to the
calling app? What would happen if our dylib-based looks used
microsleep or some such (thinking off the cuff here)?
Tim
--
Tim Jones
[EMAIL PROTECTED]
_______________________________________________
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>
