Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merged PR 623: Fix one handed only manipulation not responding if gra…
…bbed by both hands Currently if you set a generic manipulator to use only one handed manipulation and grab it with both hands it will no longer respond to interactions. Fixing this at the GrabTargetComponent level gives a better user experience as we can prevent the second grab entirely instead of just ignoring the second pointer, which is what MRTK-Unity does. * Move the _ManipulationModes_ setting up to the `UxtGrabTargetComponent` and rename it to _GrabModes_ * Update the `UxtGrabTargetComponent` to: * Only accept grab pointers up to the _GrabMode_ limit * Trigger grab/release events when it's grab mode has been satisfied and not for every grab (e.g. when using only two handed grabs, a grab event is only triggered when both hands are grabbing the object) * Improve the `UxtGrabTargetComponent` tests * Clean up exiting interaction tests * Introduce tests for focus/grab events * Introduce tests for grab mode settings * Up the limit on when to use unity builds for the tests, as they cannot compile in a unity build Related work items: #827
- Loading branch information
Carl McCaffrey
authored and
Carl McCaffrey
committed
Nov 24, 2020
1 parent
f658805
commit 692c336
Showing
14 changed files
with
566 additions
and
295 deletions.
There are no files selected for viewing
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
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
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
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
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
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
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
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
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
Oops, something went wrong.