RangeCriterion causes exception when using a double as the max

[User (Old forums)]

#16750 |

Using a double value that has a decimal part causes the RangeCritierion (or something) to throw an exception when a ValidationProvider attempts to validate with it.  Setting the DataType to Double, and Max to 9999.9999 causes the exception to occur.  Changing Max to 9999 allows it to work fine.  The documentation says the Max property must be of the same type indicated by the DataType property, which 9999.9999 certainly is.  So how are you supposed to specify a Max with a decimal or is this simply not possible?

Imported from legacy forums. Posted by Nick (had 2182 views)

[User (Old forums)]

#16751

This is a bug, and is due to the fact that the control uses the CurrentCulture to get the current decimal separator and ignores the ones set on the WinNumericTextBox.  We have filled a bug report for this, and it will be corrected in a subsequent version.

Imported from legacy forums. Posted by André (had 220 views)

[User (Old forums)]

#16752

Thanks for the update.

Imported from legacy forums. Posted by Nick (had 472 views)

[Xceed Support]

#16753

Xceed Software has just released a new package that addresses your issue.

Please download and run the latest package installer from the Xceed Website (www.xceed.com) on your computer in order to update your references. Thank you for your patience.

Imported from legacy forums. Posted by Mohamed [Xceed] (had 2510 views)

[Author]

Posts