I entered the value of “1000“ purposefully to show the tooltip saying that the value is out of range. Please also note that I set the value of Right Shift thus allowing for one digit after the decimal point. As can be seen the allowed max value is given as 655.35.
Now I enter the value of 655.3 which is clearly less than 655.35 and has exactly one digit after the decimal point.
I get the following:
(the second embedded image couldn’t be uploaded):
Maximum
655.3
Hover-over Tooltip: Must be a valid number → Save Button is disabled
After this I can only enter 655, i.e. the nearest integer that is less than 655.3.
My question: is this behavior as per design? If so, I can’t seem to find any reference to the fact that the min/max values may be only integer numbers.
If this is the case, the message of the hover-over tool tip is pretty confusing.
This is indeed confusing. Currently both the maximum and minimum field don’t support floating point number input values at all. The register configuration has no impact on this. The placeholder value is calculated correctly but the input field remains integer-only.
This exact same issue is also present for input values in the Fieldbus widget. Although there ist is not so apparent because we don’t provide a confusing placeholder there.
Ultimately there is no reason why we shouldn’t allow floating point numbers in all of these fields. We should change that. Devices need to perform the reverse conversion on set-values in any case whether they are capable of handling floating point numbers or not.
There is a corresponding support ticket about this. I have already move that to the queue of upcoming topics. I cannot commit to when we will be able to schedule work on this item in particular.
