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. But I use it nonetheless in my code. Just don't put it anywhere else than in your main thread like in buttons or other threads and you should be fine. (Of course don't put Socket.Poll in buttons or other threads either, or possibly other commands that I personally don't use frequently.) Cheers, Marc On Apr 26, 2007, at 3:13 AM, [EMAIL PROTECTED] wrote: > On Apr 26, 2007, at 00:08 UTC, Tim Hare wrote: > >> I seem to recall something about an UpdateNow method or some such >> that is required on the Mac during heavy processing because of the >> Mac's double buffering. Don't know if that pertains here or not. > > Not really. It's for situations where you're drawing directly to a > window.graphics or canvas.graphics, in a tight loop, and want this > drawing to appear right away rather than the next time through the > event loop. That's not what's going on when you change the value of a > StaticText. > > Best, > - Joe > > -- > Joe Strout -- [EMAIL PROTECTED] > > > _______________________________________________ > Unsubscribe or switch delivery mode: > <http://www.realsoftware.com/support/listmanager/> > > Search the archives: > <http://support.realsoftware.com/listarchives/lists.html> _______________________________________________ Unsubscribe or switch delivery mode: <http://www.realsoftware.com/support/listmanager/> Search the archives: <http://support.realsoftware.com/listarchives/lists.html>
