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.
reusable and pass-through configuration definitions
kyle_altendorf
Member Posts: 29 ✭
I have been doing several layers of configurations with each passing through to a derived part with a subset of the configuration parameters. Specifically, I have a core skeleton of a gridfinity unit (using for learning onshape as much as anything) with properties like x/y/z unit dimensions, and a few other things. I derive that into a part studio for a base unit, and derive that into a part studio for a grid of the base units… and similar for the bins. So, I pass those x/y/z configuration parameters through each part studio layer of derivation. This gets a bit tedious. :] I started to look at variable studios but they aren't just a definition of a group of 'values', perhaps like a struct or mapping in more coding-like terms, but more like a group of global variables with single universal values.
It seems like it would be really useful to be able to 1) define 'structs'/mappings/'objects' and 2) to be able to easily pass them through from one configuration to a 'sub'-configuration.
I've got lots of air quotes here so hopefully it ends up making sense…
Cheers,
-kyle