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.
Search
-
Re: A few expression tips.
-
Re: Struggling with partstudio import "namespace"... (plus importing variable values from partstudio)
Update: I figured out my issue with the getVariable! I had tried: getVariable(importedPS, "variablename"); But I finally figured out I needed to add the "()" to get the actual context: getVariable(importedPS(), "variablename"); The map looks like it's going to work fine, I moved it to a separate featurestudio to clean… -
More informative error messages?
When entering a formula, it would be very helpful to have more informative error messages, including e.g.: * "Units mismatch, expected length found mm^3" * For an invalid parameter, *WHICH* parameter is invalid? First one that's invalid, anyway. * "<variableName> out of range, expect 0..100000mm was -3.2mm" -
Re: AddInstance import issues with Configuration Table Part Studio
-
Re: Improvements to Onshape - August 16th, 2017
-
Re: using configurations, . 2-3 month conclusion.
Perhaps it is possible through the API, but I'm not sure how to get the individual values from a configuration list. Here is something that is possible: storing arrays and maps (these are basically lists) within a studio variable, then accessing those values from the list with an integer or string in the assembly. Map… -
Re: Quick straw pole - how are you using Onshape?
+1 for Bruce's no.4 my no.5 - variables were introduced recently and I'm using them a lot to drive the model. Instead of value, you add predefined #variablename in dimension dialog - these can replace the need for some constraints and are easily editable unlike constraints. The difficult thing with constraints is that… -
Re: Subdivide an element
Hi @baumar , To answer your question to the best of my ability: Variables exist within the context of one part studio, they are not global to a document, and therefore cannot be used in an Assembly or a Drawing. Variables can be used in all input boxes of a part studio (with a small few exceptions). Variables are just…
8 results