This repository was archived by the owner on Jul 22, 2024. It is now read-only.
Fix controller state on Daydream devices.#1384
Merged
Merged
Conversation
On Daydream devices when the activity was paused, the controllers would get disabled in BrowserWorld but not in the DeviceDelegate so when the activity would resume, the controllers in the DeviceDelegate would never re-enable the controller models in BrowserWorld.
MortimerGoro
approved these changes
Jul 11, 2019
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
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.
On Daydream devices when the activity was paused, the controllers would get
disabled in BrowserWorld but not in the DeviceDelegate so when the activity
would resume, the controllers in the DeviceDelegate would never re-enable
the controller models in BrowserWorld.