Fluid UI by updating sensors in a background thread. #626
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
On computers with lots of devices/sensors, the timer update routine will cause a performance hit on the main window redraw when moving it around. This commit address the issue by moving the timer routine to a backgroundworker object that does the work in an async manner (thread).
Test case: i7 11700, 32GB RAM, RTX2060, 165hz GSYNC monitor, 1TB nvme (plus many other HDDs hooked up).
Before background thread:
https://user-images.githubusercontent.com/25939765/149438820-aa88634a-f634-4d60-b25f-f1b445799e2c.mp4
After background thread:
https://user-images.githubusercontent.com/25939765/149438827-4c2c196f-d61a-4847-9430-2ff409e03623.mp4