You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On the web demo, the UI stops repainting after you click anywhere, and only starts again when you move the mouse. Also, when you press Ctrl+C, it pauses for a fraction of a second. This does not affect the native desktop demo.
To Reproduce
Steps to reproduce the behavior:
Open the web demo
Select continuous mode or open something that is animated, like plot demo or the fractal clock
Click anywhere on the screen and leave the mouse completely still
The UI stops repainting until you move the mouse
Expected behavior
The UI should continue to repaint as normal after clicking or pressing Ctrl+C.
Screenshots
web_demo_click_bug.mp4
Desktop (please complete the following information):
OS: Fedora 38, Windows 11
Browser Firefox
Version 120
Smartphone (please complete the following information):
(not tested)
Yes, one effect of that is that all animations freeze when you click. My guess is that the click event resets the "needs_repaint" flag somehow, no matter how many widgets called request_repaint on that frame. And so it doesn't repaint again until it gets an input event. There are a lot of changes in that PR related to that, but I don't understand it well enough to see where the problem is.
Note that this bug is not in the 0.24 release AFAICT, as it was introduced yesterday just after the release.
Describe the bug
On the web demo, the UI stops repainting after you click anywhere, and only starts again when you move the mouse. Also, when you press Ctrl+C, it pauses for a fraction of a second. This does not affect the native desktop demo.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The UI should continue to repaint as normal after clicking or pressing Ctrl+C.
Screenshots
web_demo_click_bug.mp4
Desktop (please complete the following information):
Smartphone (please complete the following information):
(not tested)
Additional context
This seems to have been caused by #3623.
The text was updated successfully, but these errors were encountered: