This application has a for loop that calls a large function:
"foreach (string invoice in listBox2.Items)"

and causes the window to turn white and loose view of all control.
How can I keep this from happening?
Thanks,
Trint

Hi Trint,

If I understand your problem correctly the whiteness is caused by a busy
application not having the time to repaint the controls. To solve this
you could handle the foreach loop in a different thread, keeping the GUI
thread up to speed, or call Application.DoEvents() ever so often inside
your loop to handle any waiting events.

On 15 Mar 2005 06:05:05 -0800, trint <(E-Mail Removed)> wrote:

> This application has a for loop that calls a large function:
> "foreach (string invoice in listBox2.Items)"
>
> and causes the window to turn white and loose view of all control.
> How can I keep this from happening?
> Thanks,
> Trint
>



--
Happy Coding!
Morten Wennevik [C# MVP]

Hi Trinity,

Run this large function in a new thread.

--
Regards,
Peter Jausovec
(http://blog.jausovec.net)
"trint" <(E-Mail Removed)> je napisal v sporocilo
news:(E-Mail Removed) ...
> This application has a for loop that calls a large function:
> "foreach (string invoice in listBox2.Items)"
>
> and causes the window to turn white and loose view of all control.
> How can I keep this from happening?
> Thanks,
> Trint
>

Thanks, I will try putting in a separate thread.
Trint

hi,

Just be aware that you should access the UI from the worker thread.

cheers,

--
Ignacio Machin,
ignacio.machin AT dot.state.fl.us
Florida Department Of Transportation



"trint" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Thanks, I will try putting in a separate thread.
> Trint
>

<"Ignacio Machin \( .NET/ C# MVP \)" <ignacio.machin AT
dot.state.fl.us>> wrote:
> Just be aware that you should access the UI from the worker thread.

Just to correct Ignacio's typo:

Just be aware that you should *not* access the UI from the worker
thread.

See http://www.pobox.com/~skeet/csharp/winforms.shtml for more
information.

--
Jon Skeet - <(E-Mail Removed)>
http://www.pobox.com/~skeet
If replying to the group, please do not mail me too

As others have pointed out, using a separate worker thread will free up
your main UI thread and your application will become responsive.

I have found the following article by Jason Clark to be helpful in
Windows Forms:

http://msdn.microsoft.com/msdnmag/issues/04/01/NET/

He shows how to use ThreadPool class in a WinForm.

-----------
Ajay Kalra
(E-Mail Removed)