Proper update/draw rate loop handling with Pyglet 3#2845
Merged
Cleptomania merged 1 commit intodevelopmentfrom Apr 24, 2026
Merged
Proper update/draw rate loop handling with Pyglet 3#2845Cleptomania merged 1 commit intodevelopmentfrom
Cleptomania merged 1 commit intodevelopmentfrom
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Pyglet 3 has some changes with the event loop interval handling. Largely this isn't really changed much on desktop, but there are a lot of special considerations when running in a browser with pyodide. This basically adds a separate event loop that handles itself differently in the browser in order to achieve the same results as desktop, while being limited by the requestAnimationFrame rate of the browser, which is tied to the monitor refresh rate.