spinner workaround#85
Merged
clefebvre merged 1 commit intolinuxmint:masterfrom Jul 20, 2019
airbusa320:spinner
Merged
Conversation
Member
|
The analysis is good... but it should be against gnome-bluetooth directly. It's a bit hacky to do this on our end. We also lose the information that the list is being refreshed. I'll merge it though as it affects CPU by default. |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
I've tracked the issue described in #55 and found it happens when the spinner is rendered and this could be a GTK bug (there are some bug reports about spinners CPU usage).
I've added a couple of lines of code to stop the spinner instance as a workaround and it works, but the user has no feedback on the scanning process...