'Kivy Clock: When to Use, Best Practices
As I go deeper into coding a GUI, I'm starting to worry that I'm not using kivy.Clock when I should be. Right now, with a small number of widgets and limited functionality, everything is populating and behaving as expected. But as the app grows, I'm concerned that some screen elements won't show up where/when they're supposed to.
I've read the docs on kivy.Clock. They spend a lot of time talking about timing operations. But there doesn't seem to be much guidance on using it for general construction of custom widgets to ensure "robustness?"
Are there conventions/best practices on when to use kivy.Clock to schedule code?
- Should all add/remove widget calls be grouped and scheduled?
- Should any statements that redraw the app be scheduled?
Apologies in advance if I missed this information in the docs. Any guidance will be deeply appreciated.
Sources
This article follows the attribution requirements of Stack Overflow and is licensed under CC BY-SA 3.0.
Source: Stack Overflow
| Solution | Source |
|---|
