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.
Why can't we fill in Variables into dimension fields, while drawing a sketch?

For example, when drawing circles in a sketch, the dimension field offers to fill in a dimension. This works, as long as you input a number.
But why won't it accept variables? You have to stop drawing circles or draw a bunch of them and take an extra step for dimensioning them with variables. This costs time and interrupts the workflow.
Tagged:
0
Answers
Perhaps you have already discovered that you can enter a variable by first entering a number, backspacing and then call up a variable or create a variable with the # key. It's annoying that entering the # symbol immediately results in a change to the left view. - Scotty
@robert_scott_robert_scott_jr_ That kind of 'workaround' isn't what I'd call a professional approach. Yes, I've done it this way, too.
But I think, Onshape should change this glitch.
Are you trying to use variables that already exist? Are they above the sketch in the feature list?
Else, the easiest way is to create variables in the variable table. The
#
approach is more versatile, though, in that it also lets you create configuration variables.I think the problem is that this could interfere with keyboard shortcuts, for example right now if you have just drawn as circle and press "L" it will switch to the line tool.
However there is no need to type a number and delete: just type "=" (as you would when you want to enter a formula in Excel) and then you can start typing the first letters of your variable …
That's not the problem. It's about the dimension field not accepting variables entered (without some weird workaround). Naturally I have variables defined already - mostly as configuration variables.
Sometimes I wonder, why people try to find excuses why something does not work. Problems and inconveniences ask for being solved, not excused.
At the moment when the dimension input field is open and focused, only numbers are accepted. If the first input is a '#', then variables should be accepted and keyboard shortcuts ignored as long as the input field has it's focus. Coding that isn't rocket science. And btw. otherwise any shortcut should fire, when editing any input field, if that hadn't already been suppressed.