The widget constantly uses 2-5% of CPU time, which is notably higher than other idle applications (even Chrome/Firefox dip below this when i am not interacting with them).
Hm yeah I can confirm this. I wonder if it has something to do with holding on to the same weather object the whole time. Maybe we should destroy it and grab a new object when we update?
The widget constantly uses 2-5% of CPU time, which is notably higher than other idle applications (even Chrome/Firefox dip below this when i am not interacting with them).