Clock iteration warning when changing to a screen with an actionbar
See original GitHub issueI’ve included a minimal working example in this gist.
One one screen, I have an ActionPrevious with a non-default app_icon. When I switch to that screen, the Clock throws the following warning:
[CRITICAL] [Clock ] Warning, too much iteration done before the next frame. Check your code, or increase the Clock.max_iteration attribute
Changing to the default icon removes the warning, as does having the ActionBar outside the ScreenManager. I’m guessing it’s a problem with animating the transition, but I’m not sure.
Issue Analytics
- State:
- Created 7 years ago
- Comments:8 (5 by maintainers)
Top Results From Across the Web
Another: Warning, too much iteration done before the next frame
When I run my script, I get this error: [CRITICAL] [Clock ] Warning, too much ...
Read more >Clock object — Kivy 2.1.0 documentation
The Clock object allows you to schedule a function call in the future; once or repeatedly at specified intervals. You can get the...
Read more >Clock Max Iterations - Google Groups
[CRITICAL] [Clock ] Warning, too much iteration done before the next frame. Check your code, or increase the Clock.max_iteration attribute.
Read more >Action indicators and action list - ReSharper - JetBrains
Action indicators are icons that, depending on your settings, appear in the Action bar, in the left margin and/or the body of the...
Read more >About the Solution - TCS iON Help Central
iON Action Bar is an easy-to-use search mechanism that enables you to quickly access solution screens, transactions, workflows, help links, reports and users ......
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I am getting the same issue. The screen loads properly but I keep getting this warning in a infinite loop. I set the Clock.max_iteration = 20 and it’s not working.
I have the same issue and haven’t find answer to it. the interface works fine but the warning keeps coming in my terminal.