Try to fix visualiser CPU issue #294
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Hi, i have the visualiser working since yesterday with no CPU issues, i have some issues with Mpris and Upower but i think its my system.
Im going to make a clean install of my system on this days and will try it again. |
|
That's amazing news. I'll tidy this up and get it merged then. Do let me know if you're still having issues with those other widgets. It could be because one of the recent changes, which introduces hooks for some widgets (including those two), requires the latest qtile-git version. |
elParaguayo
force-pushed
the
visualiser-v2
branch
2 times, most recently
from
37deeb8 to
21b2afd
Compare
This adds more stringent checks to prevent multiple calls to draw which result in constantly increasing CPU usage.
elParaguayo
force-pushed
the
visualiser-v2
branch
from
21b2afd to
5c10884
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This may be the fix to the visualiser CPU bug. Needs people to test!