GAH %$#!^ Trolled again! (user parameter entry bug is really, really not fixed)

[bentwookie]

Reading the release notes, I was soooo excited for this release:

Parameter naming issue fixed

If you noticed that pulling up custom parameters within commands became infuriating, then what you noticed was a troll bug trolling you for attention. As you started typing your custom parameter name in command dialog entry field and in mid typing, Fusion 360 would fire off a totally different command. Not cool man, not cool. The troll bug has now been taken care of.

Now I've got two trolls in my life, you guys and this bug. It still happens the same way it always has:

1) Make a sketch

2) Make a circle

3) Start typing a customer user parameter name into the entry box

4) Focus goes back to the main window and pretty soon you're issuing commands you don't intend to...

I'm trying so hard to be patient, but this is ridiculous. It's been MONTHS and this an incredibly easy bug to reproduce. Nobody needs to invent a new form of calculus to understand why QT is yanking the focus away from your textfield. 

I'd post a new Screencast, but that's busted too. Instead, I've attached a sample of it rooting through every window I have open before deciding to root through every window I have open again X infinity. 

Love you guys...getting a drink now. 

[daniel_lyall]

You just need to type faster 

[bentwookie]

"Why are all the variables in this document named a, b, c, d? And why are you drinking so much coffee? And why have you written lldb; attach<pid>; b QWidget::focusOutEvent all over all your things?"

<backs away slowly>

[daniel_lyall]

What the

[Phil.E]

@bentwookie

Two questions:

What build are you running and can you just paste the link to your screencast?

[bentwookie]

2.0.2727

Unfortunately I can't get ScreenCast to work anymore. I've posted in the ScreenCast forum about that. Here's a post of mine that has both a ScreenCast and a design link from before.

https://forums.autodesk.com/t5/design-validate-document/exasperating-bug-while-entering-dimension-ex...

Same steps yield the same results today.

Some other info (diags file attached)

[GPU Information]
GPU Device: AMD Radeon Pro 460
GPU RAM: 4096 MB
GPU Driver API: OpenGL

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

[Limit effects to optimize performance]
Off

[bespenship]

@bentwookie - our apologies and you are right.  We do have a fix for that issue that was intended to go out with Monday's update, but it has broader impact and caused problems in other areas that were discovered late in the cycle, so we backed out the code last week that would have fixed this and did not pull that information out of the "What's new?" post.

Thank you for calling this out - we need to do a better job of ensuring late changes are accurately reflected in our forum information.

The silver lining is that the fix is still valid and will be included in the next update - we just need the time to deal with the unintended impact of this change in other areas.

Thanks again and cheers.

[bentwookie]

Thanks for the update. Glad the fix is getting extra testing.