1

Closed

Worker thread does not stop if tree selection changes

description

If you select something that needs more significant CPU time to prepare (like 2000 icons) and then select something else, the worker thread still keeps one core in full load until finished.
 
You should go for stopping it somewhere in a BeforeSelect event if selected node changed and worker thread is active.
Closed Apr 10, 2009 at 9:31 PM by W3bbo
This was fixed as part of the other issue relating to the BackgroundWorker being busy.

comments