You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently the ZED codebase doesn't seem to use namespaces everywhere. Some parts do (e.g. the SDK/NativeInterface classes use namespace "s1"), while the majority of classes don't (e.g. SDK/Helpers/Scripts). This may cause conflicts with other plugins and assets when imported in Unity.
Specifically, I recently ran into a problem using ZED and UMA. UMA defines its own helper classes under its own namespace, which includes a class ReadOnlyAttribute to manage read-only attributes. Similarly, ZED defines a ReadOnlyAttribute class, without namespace, causing a conflict.
The text was updated successfully, but these errors were encountered:
Currently the ZED codebase doesn't seem to use namespaces everywhere. Some parts do (e.g. the SDK/NativeInterface classes use namespace "s1"), while the majority of classes don't (e.g. SDK/Helpers/Scripts). This may cause conflicts with other plugins and assets when imported in Unity.
Specifically, I recently ran into a problem using ZED and UMA. UMA defines its own helper classes under its own namespace, which includes a class ReadOnlyAttribute to manage read-only attributes. Similarly, ZED defines a ReadOnlyAttribute class, without namespace, causing a conflict.
The text was updated successfully, but these errors were encountered: