On Mar 29, 2007, at 15:40 UTC, Peter K. Stys wrote: > At the same time, most often i want to run a batch operation like > John, and all i want is the progressBar or a staticText value to be > updated. So I use App.DoEvents, with no obvious issues.
Ow! Reminds me of the guys driving down the freeway at 80MPH on motorcycles without helmets. They haven't run into any obvious issues yet either. > RS says don't!, use a thread instead. but I need my batch operation > to run synchronously with the rest of my app (ie. user can't > continue doing anything else until the batch finishes). So now what? So you display a modal dialog. That's what they're for. > I understand how App.doEvents could be hazardous to your health. > Instead, wouldn't it be just plain nice and simple if my loop could > call myWindow.refresh at each iteration and this would simply do what > everyone expects it to do: update the state of all controls in said > window? No, it wouldn't, because your users would still be unable to browse the menus, or move the window, or avoid the Spinning Beachball of Apparent Death, or otherwise have a pleasant user experience. 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>
