On Apr 04, 2007, at 18:23 UTC, Daniel Stenning wrote: > It does seem to me a little "overkill" to have to write the code to > spawn an extra thread just to handle what is essentially a single > threaded task that merely needs to update the screen once in a while > ( if that is what your article proposes ).
Does it? That's odd. It seems perfectly normal and appropriate to me. That *is* the correct way to do what you're describing. > Its not as my app needs to be running several processes at once. No, but it does need to be running two threads at once: one to do the processing, and one to service the UI. Best, - Joe -- Joe Strout -- [EMAIL PROTECTED] Verified Express, LLC "Making the Internet a Better Place" http://www.verex.com/ _______________________________________________ Unsubscribe or switch delivery mode: <http://www.realsoftware.com/support/listmanager/> Search the archives: <http://support.realsoftware.com/listarchives/lists.html>
