numeric set parameter: not possible sometimes due to range check

• Mar 11, 2019 - 15:36
Reported version
3.0
Type
Functional
Frequency
Few
Severity
S4 - Minor
Reproducibility
Always
Status
active
Regression
No
Workaround
No
Project

it seems that the range check for numeric parameters is contra-productive sometimes.
If I try to set the max. system distance to e.g. 13, it won't let me do so by explicit entering the number.
I double-click the number (which is getting blue then) and enter the first digit (1): immediately the value is set to 8.5 (which is the min. system distance). Whatever I try, I am unable to set the value to 13 (ok, I can enter 813, and then delete the 8... but this is crude...).
I propose to change the range check in a way that the check only applies when the field looses focus. Also the application of the changed value to the score should only apply then.
When using the spin buttons, everything is fine - but this is sometimes less efficient than setting the number explicitly.