Closed airbusa320 closed 5 years ago
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.
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...