Skip to content
This repository has been archived by the owner on Sep 1, 2023. It is now read-only.

Worker thread does not stop if tree selection changes #26

Closed
Dobby233Liu opened this issue Sep 1, 2023 · 1 comment
Closed

Worker thread does not stop if tree selection changes #26

Dobby233Liu opened this issue Sep 1, 2023 · 1 comment
Labels
Component-Resourcer Priority-Low Type-Issue

Comments

@Dobby233Liu
Copy link
Member

creation date = 2009-03-04T14:23:45.177-08:00

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.
@Dobby233Liu
Copy link
Member Author

closed date = 2009-04-10T14:31:47.96-07:00

This was fixed as part of the other issue relating to the BackgroundWorker being busy.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
Component-Resourcer Priority-Low Type-Issue
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@Dobby233Liu