Rhyme or reason for when field captures parameter names vs calculated results?

Rhyme or reason for when field captures parameter names vs calculated results?

bentwookie
Collaborator Collaborator
420 Views
2 Replies
Message 1 of 3

Rhyme or reason for when field captures parameter names vs calculated results?

bentwookie
Collaborator
Collaborator

Sometimes when I enter a parameter name (or expression involving multiple parameters) the app captures the calculated value instead of the actual parameters names. Consider

 

ParamA = 1mm

ParamB = 2mm

 

I specify an Offset in a sketch and type into the entry field "ParamA + ParamB"

 

Sometimes what's recorded is 3.0 when what should be recorded is fx:(ParamA + ParamB). If I go back and change ParamA or ParamB, the sketch offset doesn't change like it should. When I catch it displaying 3 vs fx:3, I go back and fix them up. Usually then it grabs the parameter names. 

 

It's always felt like a bug, but it's happened for so long I've started to wonder if there's some way I'm accidentally triggering this behavior. Thoughts?

0 Likes
421 Views
2 Replies
Replies (2)
Message 2 of 3

jeff_strater
Community Manager
Community Manager

rhyme, yes, reason, no.  This is a bug.  Forward creation of a sketch offset does not capture the equation, while editing any sketch dimension (including the offset dimension) does.  This one is embarrassing (there are more like this in primitives).  I'll try again to get this escalated.

 

Jeff

 


Jeff Strater
Engineering Director
Message 3 of 3

bentwookie
Collaborator
Collaborator

Much appreciated! 

 

(While you've got your escalation wand out, can we get the entry text field to grow as text is entered? I can never see what I'm typing)

0 Likes