On Mar 24, 2007, at 4:55 PM, Tim Jones wrote: > On Mar 24, 2007, at 1:49 PM, Aliacta wrote: > >>> I would rather not put the batch into a thread; if I do this i will >>> have to manually inactivate menus other user interactions. I like >>> the >>> fact that user interaction is highly restricted during batch >>> processing. Plus, putting batch execution into a thread might be >>> slightly slower. >> >> I guess with App.DoEvents you'd have to deactivate your menus and >> other user interactions as well, so you might as well go with a >> thread then. I know of no methods to keep parts of the user >> interface responsive and others not, unless you disable/enable them >> yourself. > > However, if you keep the DoEvents period short (say 5 ms), there > shouldn't be much of an opportunity for things to go awry. I've not > seen it as an issue in 5 tools that use it regularly to update the UI > elements while a long process is running.
I've seen lots of issues with the use of App.DoEvents in GUI apps. Charles Yeomans _______________________________________________ Unsubscribe or switch delivery mode: <http://www.realsoftware.com/support/listmanager/> Search the archives: <http://support.realsoftware.com/listarchives/lists.html>
