Descriptive Problem Summary:
It seems flick() now causes some irregular frame delays. Some frames will be displayed longer than they need to while others will be dropped entirely.
Numbered Steps to Reproduce Problem:
I've built a test case you can download here.
In the demo you'll find several rows of blocks. Blocks with an "M" for an icon are animated manually, each tick their icon_state is changed to form an animation. The rows with an "F" animate using flick().
TestBug() will show how the timing is off on all of them in 494 and 495. Reverting to 493 will show them animate correctly.
FirstFrameFail() may be an unrelated bug or just my confusion, but in that command the first frame of animation for the manually animated blocks will fail to be displayed.
Animations sould be perfectly in sync.
Using flick() causes irregular delays.
Does the problem occur:
Every time? Yes.
On other computers? Yes.
Did the problem NOT occur in any earlier versions? This seems to be a bug introduced in 494.