Drawing a line:
V5, V6:
1] Line, click to give start point, input “25”, press enter = constrains the line on screen to 25 units long.
2] A left click draws a line 25 units long and finishes the command.
3] OR Pressing enter again gives feedback of potential endpoints, so you can for example align the end point up with an existing entity. A left click then sets the endpoint and finishes the command.
4] OR pressing enter without setting a end point finishes the command with no line drawn.
V7, V8:
1] line, click to give start point, input “25”, press enter = constrains the line on screen to 25 units long.
2] A left click OVERRIDES the length constraint and draws a line of a length based on where the cursor is on screen when the mouse is clicked, and finishes the command.
3] OR Pressing enter again gives feedback of potential endpoints, so you can for example align the end point up with an existing entity. A left click then sets the endpoint and finishes the command.
4] OR pressing enter without setting a end point, draws a line 25 units long with its end point wherever the cursor was when the enter key is pressed.
While its arguable that the V7 / 8 behavior in point 4 is a better or at least more expected result than previously; the behavior in point 2 is definitely not.
There is no way that setting a length constraint for a line should be able to be overridden mid-command without the user deliberately specifying an alternative numerical constraint – allowing a mouse click to set an unknown length AND finish the command without confirmation of the result is not on.
Generally when creating a 2D drawing, where this command is used a lot, you get used to the visual scale of the drawing, and will often, especially when drawing with ortho on, click to set the endpoint of the line pretty close to where it would be at that length relative to other entities.
So its easy to miss that when you thought you were placing a line 25 units long, in actual fact its 26.5 or 23 or something – an unwanted result that should not be possible, and was not possible in V5 / V6.
Please adjust this command to behave as V5 / V6.
Note: - this overriding of the numerical input occurs with other input also – move, circle (by centrepoint), and probably a stack of others…