Inventor 2022 Keyboard Shortcut Bug?

Cadderman
Enthusiast
Enthusiast

Inventor 2022 Keyboard Shortcut Bug?

Cadderman
Enthusiast
Enthusiast

Hi all,

 

I have encountered a problem on Inventor 2022 and I think it's a bug.  The issue is in sketch mode and only occurs when I open a certain part.  I am trying to use "L" for "Line", but it doesn't activate the "Line" command immediately.  Instead, the   command line at the bottom shows up/down arrows and I have to cycle and press enter to activate the command.  

 

If I open Inventor 2022 and create a new part, under the same project folder, I can use L in sketch mode as normal - it immediately activates the command.  However, once I open up the skeleton to my entire assembly, I try to use L in sketch mode and I need to cycle the commands and press enter to activate.  If I then make a new part in the same instance of Inventor, I press "L" and it requires me to press enter again.  

 

It all seems a bit strange.  I have looked up similar issues and ensured "Use default multi-character Command Aliases" is unticked.  Any ideas?

 

 

Reply
296 Views
2 Replies
Replies (2)

mcgyvr
Consultant
Consultant

Go to the Customize dialog box/keyboard tab.. Click on the "Keys" column to sort by that and scroll down to the "L" section and then post a screenshot like this.. Do you have multiple commands assigned to the "L"?

mcgyvr_0-1651504719110.png

 

 

 



-------------------------------------------------------------------------------------------
Inventor 2023 - Dell Precision 5570

Did you find this reply helpful ? If so please use the Accept Solution button below.
Maybe buy me a beer through Venmo @mcgyvr1269

Cadderman
Enthusiast
Enthusiast

Yes, it is the same in both Inventor 2021 and 2022 on my PC.  I have removed the "L" and "LS" commands on 2022 and now the line command works fine in sketch mode. 

 

It leaves me wondering why it was not a problem even once on 2021 but is a repeating issue on Inventor 2022.  I thought it was project file specific but I was working on another job and it started occurring after a short while.

 

 

0 Likes