you could use Application.DoEvents(). But as experts in this (and other
dotnet groups) would agree, You should avoid using DoEvents and rather use
Threads. Read up on threads - it shouldn't be too much of an effort. In the
end, it'll be worth it.
The idea is to have your long operation run on a seperate thread so that the
main thread (one that the UI is running on) is free to process window
messages.
hope that helps..
Imran.
> Hi,
>
[quoted text clipped - 6 lines]
> Thanks
> Martin
Martin - 24 Sep 2004 20:09 GMT
DoEvents is was I was looking for - I actually want to give feed back on the
long operation whilst it is going on by writing to a log window.
This is just a little utility app so I think DoEvents will be enough for me.
Thanks for the speedy reply!
Martin
> you could use Application.DoEvents(). But as experts in this (and other
> dotnet groups) would agree, You should avoid using DoEvents and rather use
[quoted text clipped - 18 lines]
> > Thanks
> > Martin
Hi
You can put your processing in a class and interact with UI with events
this is an excellent exemple ( in french :S but the code is easy to
understand)
http://blogs.microsoft.fr/pascalbe/archive/2004/09/21/227.aspx
http://www.olymars.net/Blogs/EventsDelegates/EventsDelegates.zip
it gives feedback on a file copy (time, progress...)