Exasperating bug while entering dimension expressions

[matt]

 I'm running into an annoying bug that just cropped up in the last release or two.

When entering dimension values, I want to type an expression like "material_thickness+2"

I type M A T, then tab to accept the pop-up suggestion. The dimension field now contains "material_thickness." Now, I can't type anything further. Plus, minus, parentheses, etc. do nothing.

Strangely, I discovered that some keys like 'c' will quit the dimension and initiate the command corresponding to that shortcut key; 'circle' in this case.

To workaround I can type the expression into a text editor or something, then cut and paste it into the dimension field. Sometimes I can enter things in a different order. In this case, I type +, 2, then back up to the start and type the parameter name.

Maddening!

I'm on OSX 10.12 in case that matters. Please confirm if you're seeing this bug too!

[bentwookie]

I just came to complain about (what I think) is the same thing. I've had similar issues before where the complete panel seems to end editing while completing. Only now, it's happening right off the bat. I can't do anything in the app right now. 

Here's my design:

http://a360.co/2gc9Yfx

Here's my screencast:

Note. After typing 'LED', I'm madly trying to get an M in there. None of my keypresses (other than shift) are appearing in the screencast. 

[bentwookie]

I'm running 2.0.2539

Mac OS X: 10.12.1 (16B2555)

[GPU Information]
GPU Device: NVIDIA GeForce GT 650M
GPU RAM: 1024 MB
GPU Driver API: OpenGL Core Profile

[Graphics Effects Settings]
Use high-resolution graphics: Off
Anti Aliasing: On
Ambient Occlusion: On
Object Shadow: Off
Ground Shadow: On
Ground Reflection: Off
Selection Display Style: Normal
Transparency Effect: Better Performance

[Limit effects to optimize performance]
Off

[bentwookie]

It's like there's a timer that fires a second or two after the first keystroke into a dimension text field. Once that happens, keystrokes don't go to the text field, but to the app. So you'll type something like Max and have the 'a' trigger the appearance panel to appear. 

Let me know if I can help debug. The app is 100% unusable as it stands. 

[matt]

Yes, this looks like the same thing to me.

Another workaround I discovered is that by clicking in the edit field with the Mouse I can sometimes 'unlock' the field and resume typing.  Also, by typing an operator first (like +) the expression is highlighted red until all operators are properly entered.  This sometimes allows me to get my expression entered.

Still maddening, but better than the cut/paste trick.

-Matt

[Phil.E]

(internal reference FUS-29205)

This is being investigated as a top priority bug. Thanks for your input and observations, sorry for the trouble.

Regards,

[bentwookie]

This isn't fixed in the Dec 1 release. Any hope of it getting in soon? I really have a tough time using the app at all these days. 

[Phil.E]

We are working on a fix.

In the meantime, can you try clicking on the parameters that appear on the list? The problem you are having is when using typing alone to enter the parameters, but you can also click on the dropdown list items.

So in your case, after typing LED, use the mouse to pick "LEDMinDiam". This is just a temporary workaround for you, but should get you up and running. Please let us know how it goes.

Regards,

[bentwookie]

That does help. Thanks! I used to use my mouse in that menu, but trained myself out of it after running into a different bug where moving the mouse would close the menu. I don't seem to be hitting that now though. 

[bentwookie]

Still a thing...

Clearly this can't be hitting everyone. What's different about our setup?

[Phil.E]

The problem is this is a bug that is not yet fixed. There has been progress on it weekly since it was reported. They are still looking for the cause of it. It's definitely not related to the bugs we fixed in the December 14 update that seemed similar (problems entering things in dialogs/HUD). So we need to keep digging, sorry this is still a problem. It's not at all forgotten and can be reproduced in development builds, so it will get fixed.

Thanks,

[bentwookie]

Cool. Let me know if I can help!

[Phil.E]

We have a couple of great reproducible cases. Thank you all for your patience and helping. These bugs are harder to find on some hardware, which is the main reason it's not obvious to us, but exasperating to you guys. Sorry about that.

Related forum posts:

https://forums.autodesk.com/t5/design-validate-document/user-parameters-have-become-much-more-diffic...

http://forums.autodesk.com/t5/design-validate-document/extrude-bug/m-p/6729560/highlight/false#M8553...

(internal reference FUS-29205)

[neljoshua]

@Phil.E,

I am pleased to hear this is being worked on.  I, too have seen this issue when typing dimensions in for extrusion lengths.  For example, much of the insulation we are using in our system is two inches thick.  I go to extrude a profile and type "2in" and instead of getting what I expect, the extrude command is exited and the inspected tool is opened (due to the "i" character).

I have not posted regarding this for a few reasons.  First, I was not able to reliably reproduce the issue for a Screencast.  Second, I did not notice this post earlier (or I would have added to it).  And, finally, it seems that pressing "space" between the "2" and the unit ("in") precludes this from happening, so I could keep working without too much hassle.

I am not certain if this would work for others here, as some of you were using parameters; perhaps you could try pressing "space" and then "backspace"/"delete".  It is an extra step, but perhaps it would help.

[Phil.E]

Thanks for the tips and steps to reproduce. We have a few paths to get this one, but with these hard to repro bugs, we really like to be sure the fix is good before you guys get it! This helps.

[Phil.E]

We are still working on a fix for this.

There is a workaround, click once in the canvas.

Here is an example to show you how it works:

1. New Fusion file
2. Create a custom parameter and call it "ledmodel" (without the quotes)
3. Sketch a rectangle by dragging, no text input.
4. Dimension one of the sides (after finishing rectangle command)
5. Double click the dimension to edit it
6. Click in canvas once (key step)

So after step #5 you click the canvas once, the bug doesn't happen (the dimension HUD flashes briefly but it gets focus again). It will not interpret parameter text as hotkeys.

[bentwookie]

I appreciate the reply. I'll try to bend my muscle-memory that way. It's still a bummer. You have to do everything in two steps. Make the thing and then dimension the thing (with the extra click). 

If you can say, what's the deal here? Is this wrapped up in some bigger UI overhaul that keeps slipping? Is it coming soon? If not, can we get a bandaid fix in the existing code base?

Again, is this only happening to a few of us? That text field is like step one for nearly every operation you do in this app. If it was wide-spread, this forum would look l like a bread-riot. If it's not, what's different about the configs that have this problem and the ones that don't. And how do I get into the "ones that don't" camp? 🙂

Thanks.

[Phil.E]

This happened *after the big UI overhaul. We updated a major 3rd party component that manages the UI. It's not without bugs itself as we are finding. The reason this is taking a while is cracking the code on that 3rd party thing. A bandaid is not what you want here, this is low level stuff, foundational. It needs to be a real fix.

It doesn't affect Windows as much as Mac, if at all.

Sorry for the trouble and thanks for your patience.