Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upopenxr: Handle STOPPING event and visibility state changes #139
+31
−0
Conversation
|
@bors-servo r+ |
|
|
|
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Manishearth commentedMar 25, 2020
The runtime now correctly triggers the
READYstate, and we're also now at a reasonable FPS that thevisible-blurredstate actually can occur.Tested on both examples that run at 60FPS and 20FPS (where the
STOPPINGis immediately triggered when you hit the menu button)Supersedes #109
Fixes #76
r? @jdm