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

UnityEngine namespace to avoid collisions #11600

Closed
wants to merge 1 commit into from

Conversation

ms-iankudinova
Copy link

Overview

Fixing namespace (UnityEngine.Mesh) clash, when MRTK is used with other packages.

Changes

  • Fixes: HandJointVisualizer uses UnityEngine.Mesh as a type. To avoid clashing with other types, full namespace was added.

@@ -29,10 +29,10 @@ public class HandJointVisualizer : MonoBehaviour

[SerializeField]
[Tooltip("Joint visualization mesh.")]
private Mesh jointMesh;
private UnityEngine.Mesh jointMesh;
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm curious why this change is needed? I assume you're hitting conflicts with you product namespace, but what I don't understand is why. Unless you're adding a reference to your product assemblies, I don't see how com.microsoft.mrtk.input would pick up your product's namespace.

@ms-iankudinova
Copy link
Author

We found a reason, why collision happened (our artifact was referenced inside mrtk.input). We applied fix on our side, so there is no need fot this change. I will close this PR

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