We have a number of settings on our driver that take double values and are defined by DoubleSetupFields. For all of these settings, the input value validation in XProtect Management Client fails to accept most valid values. An example image is attached.
Here is the code defining the field:
new DoubleSetupField() {
Key = Constants.TEMPERATURE_MAX_TRIGGER,
DisplayName = “Trigger Max Temperature”,
DisplayNameReferenceId = Guid.Empty,
IsReadOnly = false,
ReferenceId = Constants.TEMPERATURE_MAX_TRIGGER_REF_ID,
MinValue = -50,
MaxValue = 50,
Resolution = 0.1,
DefaultValue = 0,
},
We are also having problems with other Double fields with different min and max values (e.g. 0 - 10), so it’s not just this field.
We are using XProtect Management Client 2023 R3.