On Apr 26, 2007, at 10:32 AM, [EMAIL PROTECTED] wrote: > On Apr 26, 2007, at 11:49 UTC, Marc (aliacta.com) wrote: > >> For a simple example of what can go wrong: >> >> Connect a TCPSocket. >> >> Make a never-ending loop in the main thread with App.DoEvents. >> >> Have a button with the code "TCPSocket.Poll" or "App.DoEvents" >> >> Run, and click the button. I bet that *at least* your socket no >> longer works, even though the last time I tested this was with 5.5. >> And if you're out of luck you might not even become aware that it is >> your socket that no longer works, hence the evil nature of >> App.DoEvents. > > Agreed. LOTS of things can go wrong if you use App.DoEvents anywhere > other than for its intended use (which is creating an event-driven > console app).
If this is its intended use, then why was it even made available in GUI applications? Charles Yeomans _______________________________________________ Unsubscribe or switch delivery mode: <http://www.realsoftware.com/support/listmanager/> Search the archives: <http://support.realsoftware.com/listarchives/lists.html>
