> And I am fairly certain that it can. Jon Johnson has a nice little > article on his blog site that explains one way to set up a thread + > GUI updating. Essentially, the thread object publishes information, > and the window reads it from a Timer. I've long used a similar > scheme in one of my applications. >
First a thread, and now a timer???? What next? All we want is: for j = 1 to 1000000 myWindow.myStaticText.text = str(j) next for myStaticText to actually display the progress of the loop as it's running (distilled example of course). I accept that App.DoEvents is unhealthy, but I second my own vote for myWindow.refresh to do what one would expect: to safely update the values of all the window's controls so the user can see that something is actually happening. We all have frequent instances I'm sure where code is running iteratively, in many places and under many windows, so to have a thread for each (...then a timer...then...) is needlessly complicated IMHO. All the suggested workarounds indicate that a simple functionality is not implemented correctly. P. -- ------------------------------------------------------------------------------- Peter K. Stys, MD Professor of Medicine(Neurology), Senior Scientist Ottawa Health Research Institute, Div. of Neuroscience Ottawa Hospital / University of Ottawa Ontario, CANADA tel: (613)761-5444 fax: (613)761-5330 http://www.ohri.ca/profiles/stys.asp ------------------------------------------------------------------------------- _______________________________________________ Unsubscribe or switch delivery mode: <http://www.realsoftware.com/support/listmanager/> Search the archives: <http://support.realsoftware.com/listarchives/lists.html>
