feat(engine): follow a fold from the screens' own callbacks - #75
Merged
Merged
Conversation
The window learnt which panel the guest draws on by polling the display report once a second. Every display port vends the grouped screen callbacks on Xcode 27, and their properties callback fires on both panels for every fold about half a second before the report names the new panel. The session registers them, with the damage and surface callbacks as the fallback, and the watcher answers each announcement with a short burst of re-reads; its clock is a five second safety net.
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.
What: A foldable's window used to learn which panel the guest draws on by polling the display report once a second. Every display port vends CoreSimDeviceIO's grouped screen callbacks on Xcode 27, and their properties callback fires on both panels for every fold, about half a second before the report names the new panel. The display session now registers those callbacks (frames from
frameCallback, surfaces fromsurfacesChangedCallback), keeping the damage and surface callbacks as the fallback where a port lacks them, and publishes what each screen announces. The watcher answers an announcement with a short burst of re-reads until the report changes; its clock became a five second safety net.Closes #68.