Note that there are some explanatory texts on larger screens.

plurals
  1. POWPF user interface with long processing execution hangs
    text
    copied!<p>I am extremely Sorry for this long post. I need some help on c# wpf issues. I have build a complicated UI(somehow) and there is some buttons... like start and stop and others.</p> <p>When i click the start button a execution process starts with communicating with some protocol layer and others and it is a long process .. and during this process i have to show some notification UI like "Enter a Text", "Select Something" etc... this time i have to show some wpf window object... and after some time i have to automatically destroy the window and go with processing again.</p> <p>At first i tried to run the execution in the Main window class. But it results that when the execution starts.. user can't click anything and ui doesno't respond rather just hangs. I investigate the problem... and found that UI is busy with processing in the execution on protocol layer so its not responding.</p> <p>Here is my problem... can u give me some solution that...</p> <ol> <li>i will have 2 button..start and stop</li> <li>when i click the start button... a large process will start( like nested for loop with a large int which will continue for 50 seconds) in function named Processor.</li> <li>at time of processing the function Processor will create several window and show them wait for 5-10 seconds and also destroy them. or user click;s on the window</li> <li>And the whole time the stop button should be clickable so that when i click the stop button .. the process should be stop.</li> </ol> <p>I tried this with backgroundworker, dispatcher... and using separate thread. but no luck. I guess i am missing something. because if i wait for some result showing a window..the window will definitely hang.. and if i separate them with different thread.. it will not communicate with each other. please give me some suggestions</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload