This repository has been archived by the owner on Mar 1, 2024. It is now read-only.
Handle "defaultToHover" field in offer #60
Merged
Conversation
This file contains 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
Passed in from Streamer to indicate we're in Editor mode where locked cursor just results in not having any cursor.
lukehb
reviewed
Jan 12, 2023
lukehb
reviewed
Jan 12, 2023
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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 pull request allows the infrastructure to handle an extra field in the initial connection offer for determining whether the frontend should default to hovering mouse instead of captured.
Intended for use with editor streaming, this field has been put in the connection offer instead of its own config message to avoid an error on older infrastructure versions which will not be expecting new message types.