Add ability to create a separate render thread locked to the display refresh rate #36
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.
This PR adds the ability to init our window's view with a CVDisplayLink that syncs a separate render thread with the display refresh rate. Window now has an
on_tick, which when set, notifies the window creation method that the separate thread needs to be created and kicked off.Currently most of the code that handles this uses the view's events directly by overriding defaults like
viewDidMoveToWindow. I have started looking into how to move as much of this code to zig as possible, but currently none of it is used, and the objc code is responsible for the behavior.This PR will need to be merged before the Mach companion PR is merged.