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

[MRKT3] Making custom reticles a bit easier in MRTK3. #11758

Merged

Conversation

AMollis
Copy link
Member

@AMollis AMollis commented Aug 3, 2023

Overview

The intent of this change is to make attaching a custom reticle easier in MRTK3. The custom reticle is now attached to the base reticle's root transform, removing the need for the custom reticle to position itself.

Also, reverting changes made to RecticleMagnetism. With this change, RecticleMagnetisms once again uses an interface for setting progress, instead of requiring a RingReticle component. Also, instead of using the old IVariableReticle, RecticleMagnetisms is now using IVariableProgressReticle to better indicate the propose of the interface.

I also rename the newer IVariableReticle to IRecticleVisual to better indicate its purpose.

This change is in response to #11751

Changes

…r in MRTK. The custom reticle is now attached to the base recticle's root transform, removing the need for the custom reticle to position itself.

Also, reverting changes made to `RecticleMagnetism`, this now is using an interface again for setting progress, instead of requiring a RingReticle component.  Instead of using the old `IVariableReticle` its not `IVariableProgressReticle` to better indicate the propose of the interface.

I also rename the newer `IVariableReticle`  to `RecticleVisual` to better indicate its purpose.
@AMollis AMollis merged commit c86b0e9 into microsoft:mrtk3 Aug 4, 2023
8 checks passed
@AMollis AMollis deleted the user/amollis/mrtk3/improve-custom-recticle branch August 4, 2023 17:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants