I notice, that if you set min/max values on a RadNumericTextBox, and a user enters a value outside of the allowable range, that the text box value gets set to the min or max, depending on which side of the range the disallowed value was entered as. For instance, if the max is set to 5.5, and the user enters 6, the value of the box gets set to 5.5. I realize that there is a brief "alert" display, but this may not be noticed. I can see how this behavior might make sense in some scenarios, however, it can also be misleading, and I'm not sure it should be the default behavior. The user might not notice that the box reset to an approporiate value and may not realize what they wanted to enter was not allowed. Since precision is often key when using numeric text boxes to enter numbers, I don't think the text box should ever "assume" what an appropriate value should be if what the user entered is invalid. Rather, it should simply not allow the user to enter the value. This is the case if the user attempts to enter an invalid character. The same should be true as far as range validation. It might be nice if Telerik has some way of alerting the user that the value they entered was greater than the max or less than the min, however, i don't have a problem with it being incumbent upon us developers to display min/max values next to the textbox. Either way, when the box gets "set" to a value the user never entered, problems can occur.
I also noticed one other small issue. If a NumericTextBox is set to allow negatives (ie the min is not set to 0), and it is also set to allow rounding, and it is also set to KeepNotRoundedValue=False, and it's decimal places is set to some value, like 2, then the following can occur.
If the value entered is negative, however, when rounded, is actually "0.00", then the numeric textbox displays -0.00.
So, in my example, if the value entered was -.004. this would round to 0.00, so the display should be "0.00". However, instead, "-0.00" is displayed and -0 is not a number. If you click on the textbox, the minus sign disppears, but this shouldn't be necessary.
I also noticed one other small issue. If a NumericTextBox is set to allow negatives (ie the min is not set to 0), and it is also set to allow rounding, and it is also set to KeepNotRoundedValue=False, and it's decimal places is set to some value, like 2, then the following can occur.
If the value entered is negative, however, when rounded, is actually "0.00", then the numeric textbox displays -0.00.
So, in my example, if the value entered was -.004. this would round to 0.00, so the display should be "0.00". However, instead, "-0.00" is displayed and -0 is not a number. If you click on the textbox, the minus sign disppears, but this shouldn't be necessary.