Home/ Questions/Q 9075239
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-16T18:49:26+00:00

I Have a WPF multithread application, and each thread updates some variables of objects

  • 0

I Have a WPF multithread application, and each thread updates some variables of objects binding to the xaml gui.

If I Use a normal thread or a threadpool it works fine. Each object is being updated at real time in the GUI when the object variables is changed by the treads.

I want to use Parallel.ForEach because it stops the execution util all threads are finished. This is important to me for block the interface (because the use should wait), and for can show a finished message. The bad thing is that with Parallel.Foreach is not being updated in real time, only when all threads are finished.

This way works, but It only updates the Gui at the end.

Parallel.ForEach(Computers, new ParallelOptions { MaxDegreeOfParallelism = 1}, computer => { PingTemp(computer); });

This way works, but It doesn’t wait to the end of the ThreadPool.

Task.Factory.StartNew(() => Parallel.ForEach<Computer>(Computers, new ParallelOptions { MaxDegreeOfParallelism = 1 }, computer => PingTemp(computer)));

What approach do you recommend when the GUI is updated in realtime and wait the execution of threadpool before continue.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Do NOT do that in the same thread. If you need the user to wait, then use a mechanism where you LOGICALLY stop interaction at the UI (turn if ff, put a transparent label with a working animation on top of the window) and do things outside the loop. The whole UI interaction is blocked as long as your thread blocks.

    YOu do NOT get ANY updates in the UI while the UI thread is blocking. So, that already kills what you want. But more important – you really make bad things. ALWAYS keep the UI free.

    My old rule is 0.1/1. Everything longer than 0.1 seconds MUST go into a non-ui thread, anything longer than 1 second MUST disable the UI and show a working animation, preferably one that shows progress if feasible by any mreans.

    I use a GUI framework that handles that automatically via bound method signatures (telling the UI this method call is async, then the routine is automatically called in a separate thread).

    • 0