Welcome to the Onshape forum! Ask questions and join in the discussions about everything Onshape.First time visiting? Here are some places to start:
- Looking for a certain topic? Check out the categories filter or use Search (upper right).
- Need support? Ask a question to our Community Support category.
- Please submit support tickets for bugs but you can request improvements in the Product Feedback category.
- Be respectful, on topic and if you see a problem, Flag it.
If you would like to contact our Community Manager personally, feel free to send a private message or an email.
Namespaced enums in feature UI's
brooke_spreen Member, Developers Posts: 115 PRO
Can anyone shed some light on why enums cannot be namespaced when used in feature UI's?
Design Engineer | Anerdgy AG
This is a known shortcoming, and has not been a huge priority to address so far. The cases which hit this are usually trying to place config parameters from multiple part studios in a feature dialog. Is that the case for you?
If so, I would recommend using a reference parameter in the meantime. I know the UI is not as nicely curated as rolling your own dialog, but it's the best solution right now. We have other improvements coming next year intended to make it easier to curate a set of elements (e.g. Part Studios) intended to be used with a particular dialog.
If not, what is the problem you're solving with enums from multiple namespaces in a feature? Understanding the need can help us prioritize this issue better!
It also seems like you should be able to get away with importing the desired enums directly from their source, with no namespace, at the deisired version. You would thus use no namespace for the contents of the dialog, and namespace(s) for other conflicting imports. However, without seeing the exact structure I can't say for sure.