controls are designed to create a predefined input for a user. Basically as soon as you apply a Mask
property, this property is used to assert whether the entered value is valid or not. And by valid I mean that it matches the predefined mask.
This is why when you apply a Mask
of "n3.3", you tell the control that its value is valid and correct only when it contains 3 digits before and 3 digits after the floating point. And only when this criteria is met, the value is processed as appropriate and the underlying ViewModel
is updated accordingly.
If you want to workaround this behavior, we've exposed a property in the RadMaskedNumericInput
. Its default value is false which means that until a value matches the criteria applied by the Mask
property, it isn't considered as valid and the ViewModel
isn't updated. But as soon as you set the AllowInvalidValues
property to True
, the MaskedNumericInput
will start updating its value and the corresponding business property at every new input disregarding the Mask
And in your case, you can try setting the AllowInvalidValues
as this should lead to the results you requested. Also, I noticed that your Value
so you might want to consider changing that as well. A TwoWay
mode allows the MaskedNumericInput
control to update the business model underneath it accordingly.
I hope this information helps but please don't hesitate to write back if you have other questions.
TRY TELERIK'S NEWEST PRODUCT - EQATEC APPLICATION ANALYTICS for SILVERLIGHT.
Learn what features your users use (or don't use) in your application. Know your audience. Target it better. Develop wisely.
Sign up for Free application insights >>