Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix null ref in SpatialManipulationReticle when multiple interactables are hovered #873

Merged
merged 4 commits into from
Jul 25, 2024

Conversation

keveleigh
Copy link
Contributor

@keveleigh keveleigh commented Jul 24, 2024

Fixes #671

Ensures that we actually pass a BoundsHandleInteractable to RotateReticle, as that's what it's expecting as far as hierarchy. If we inadvertently pass the BoundsControl, the hierarchy logic is incorrect (no parent when it's in the root of the scene).

This case won't be hit in the default MRTK XR Rig. It's only when "Hit Closest Only" on a ray interactor is unchecked that this case is possible.

@keveleigh keveleigh self-assigned this Jul 24, 2024
@shaynie shaynie self-requested a review July 24, 2024 22:50
@keveleigh keveleigh merged commit 0e027dd into MixedRealityToolkit:main Jul 25, 2024
4 checks passed
@keveleigh keveleigh deleted the fix-null-ref branch July 25, 2024 16:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[BUG] SpatialManipulationReticle throws NullReferenceException
3 participants