I would like to get rid of both the features described below, which I think are redundant and frankly stupid. Failing that, please add a setting to turn them off.
I am a windows user, I am accustomed to the Windows way of doing things, Inventor only runs on windows.
On Windows, a single click selects something and the delete key deletes it.
So, to delete a constraint I click on it and press delete. But instead a little box appears to let me edit the value of the constraint, and now I have deleted the number by accident.
To delete the constraint, I must either use the right click menu, or click it a second time before pressing delete (but not too quickly, see below).
On Windows, a double click selects something and opens/activates it.
So to open up a constraint for editing, I double click it. But wait! A different version of the same little box appears.
To open and edit a constraint I have to use the right click menu, or select it (which already takes one more click than it should) and hit enter.
So, Inventor has two extra ways to edit the constraint value. These both work in a way that I would consider non-standard for a Windows program and both displace other more useful functionality to do so.
The single click behaviour is doubly redundant, given that it does exactly what a double click does, and given that it stops me selecting a constraint in the expected way. The double click behaviour is also unnecessary, because if it simply opened the "edit constraint" dialog, the constraint value is already highlighted, so you can type in the new value and hit enter in exactly the same way that the current reduced functionality works. I think that’s how it worked in old days of Inventor but perhaps I’m remembering it wrong.
I guess the reasoning must have been that editing the value of a constraint is much more common than deleting it or modifying it in other ways. In my experience this is not the case at all. I probably delete constraints or move them to different geometry at more often than editing the numbers. For me, by far the most common value for a constraint is and will always remain zero.
Even if I am an outlier, and most other users do spend lots of time editing constraint values, there was still no need to add the same functionality twice (actually thrice).
I really hope the UX team can take a look at this loose end and tidy it up.
I’m usually more hesitant when it comes to telling other programmers how to do their job. I am going out on a limb this time, I’m certain that fixing this would be trivial. Maybe 4 hours of coding absolute worst case, should be less than 30 minutes if the codebase is well structured.