Cursor demo improvement #2916
Merged
Cursor demo improvement #2916
Conversation
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
Relying on the random selection to change the color runs the risk of users being unsure if their interactions are sparking a response. For a simple test case (especially when in VR and no console log is available) a guaranteed change is much better. I made this change myself to ensure that the interactions were actually reliable and not glitchy and unresponsive as it seemed with the random selection re-picking the existing color. This should improve first run perceptions of the interaction API.
|
Thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description:
Relying on the random selection to change the color runs the risk of users being unsure if their interactions are sparking a response. For a simple test case (especially when in VR and no console log is available) a guaranteed change is much better. I made this change myself to ensure that the interactions were actually reliable and not glitchy and unresponsive as it seemed with the random selection re-picking the existing color. This should improve first run perceptions of the interaction API.
Changes proposed: