Re: Application.DoEvents() resets cursor?

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

If you accept "a time-consuming operation that doesn't let events get handled" as proper design (which I don't, by the way), _and_ you're going to use Application.DoEvents() rather than block the UI entirely, then do it right: call Application.DoEvents() periodically during your time-consuming operation, not just right when you start it.

You're "teaching your grandmother to suck eggs", here, Duniho. Why is it that everyone on these groups seems to automatically assume when they respond to a post that they're talking to an incompetent? Is it just the chronic passive-aggressive attitude that seems endemic to newsgroups?

By "time-consuming operations" I'm talking about sub-second operations for which the lack of underpainting is mererly an annoying visual glitch. It's a UI refinement, nothing more, to contribute to the professional appearance of the apps. For real "time-consuming operations" I'd customarily put them on a worker thread or throw in a DoEvents at sufficiently-short intervals to keep the app's UI responsive.

Jeez.

Tom Dacon
Dacon Software Consulting

.