On Apr 26, 2007, at 2:59 PM, Peter K. Stys wrote: > So I took your advice Joe, and transferred my batch code from a button > to a thread. I must admit the GUI is more Mac-like. Want to hear > what's ironic tho: when the thread is first run by the button, my app > "hangs" for seconds (sometimes 20 or more) at a time with the beach > ball of death until "things get going" and the main thread regains > control of the app. Previously, there was no beach ball. Curious no? > > I agree that threads are the better way to go w.r.t. Apple's GUI > guidelines. > > I will try to avoid app.doevents as per everyone's warnings. I still > maintain that myWindow.refresh should do just that, or why have this > call?
It does do just that. It refreshes the window on the next pass through the event loop, as Joe explained. When you call it in the course of a long-executing method, that next event loop iteration does not occur until some time after the method returns. Charles Yeomans _______________________________________________ Unsubscribe or switch delivery mode: <http://www.realsoftware.com/support/listmanager/> Search the archives: <http://support.realsoftware.com/listarchives/lists.html>
