Skip to content

ReadonlyAttribute in global runtime causes import issues #694

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

Open
2 tasks done
rossstyants opened this issue May 10, 2025 · 2 comments
Open
2 tasks done

ReadonlyAttribute in global runtime causes import issues #694

rossstyants opened this issue May 10, 2025 · 2 comments

Comments

@rossstyants
Copy link

Preliminary Checks

  • This issue is not a duplicate. Before opening a new issue, please search existing issues.
  • This issue is not a question, feature request, or anything other than a bug report directly related to this project.

Description

Hello, just a heads up - trying to import the Zed SDK and because we also have a ReadOnlyAttribute but without the label variable - also sitting in the global runtime - the project won't compile - your version of the ReadOnlyAttribute is not accessible - hidden inside the DLL - so it means I think that we have to go through our whole (large!) project and probably put our ReadOnlyAttribute behind a namespace - but it's quite a big edit on a lot of files...
(I can't just remove our one - because it takes different input so all of our scripts then flag errors anyway)

Steps to Reproduce

2.Create a global REadOnlyAttribute
3.Import zed sdk
...

Expected Result

compiles

Actual Result

doesn't compile

ZED Camera model

ZED

Environment

Unity 2022

Anything else?

no, that's it

@rossstyants
Copy link
Author

Ok so i could kindof resolve it with a replace all in the project - replacing [ReadOnly] with [ReadOnly("")] - but then some other packages which used their own ReadOnly tags threw up some issues (Obi) for example - but you can get there like that - still not a smooth import -

@Bvallon-sl
Copy link
Contributor

Hi,

Sorry for the late reply.
What do you suggest ? Should we put ours in a namespace?

Note that it's preferable that you directly create any Unity-related issue on the dedicated github repo (https://github.com/stereolabs/zed-unity)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

2 participants