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.
Change variable values after mergeContext / importDerived?
leon_poot
Member, Developers Posts: 87 ✭✭✭
Now, I might be dreaming, but I'd really love this to be possible.
Is there a way to Change variable values after using
I figured since variables are added to the context, these should come along. Would there at least be a way to get all variables in a context, so you don't have to look for them by name using
Is there a way to Change variable values after using
mergeContext
or importDerived
to import geometry from another PS? This would allow several morphologically different instances of the same geometry. I figured since variables are added to the context, these should come along. Would there at least be a way to get all variables in a context, so you don't have to look for them by name using
getVariable
?"A common mistake that people make when trying to design something completely foolproof is to underestimate the ingenuity of complete fools." - Douglas Adams, Mostly Harmless
Tagged:
0
Comments
Though, I'm not quite sure what you mean by "several morphologically different instances of the same geometry". Are you looking to externally change the values of variables before the Part Studio is rebuilt, to get different geometry? If so, you'll have to wait for configurations for that.
I sense a pattern here, my last three / four questions on this forum have all been answered with "be patient, configurations are coming your way soon". Which is exactly what I'll do, I'm really glad you guys are working on it.