Old Name was. "Implement a feature to change the Value property based on the Text property ". However, Value is the primary property for this control and that is why we want clients to use Value property, not two-way binding of the Text property that changes the Value internally. That is why we changed the name of the feature request.

Its meaningful and clients will benefit from it. Basically clients want the literals to be included in in the VALUE. And this is meaningful only in TextInput. So new property in RadMaskedTextInput (for ex. IncludeLiteralsInValue) seems fine - Estimate 10. 

Example Scenario: 

Mask="##--##--##", 

User types 123456, Value property becomes "12--34--56" which will have the same value as the Text property.

Example Scenario:

IP Address SDK demo. Look at its code - there is converter in file and convert methods in ViewModel.cs. Both Value and Text are bound. If Value includes the dots, only 1 converter and 1 2way bingding would do the job with less code.

Add built in masks for Email, IP, Phone, etc. Add design time support for this.

Possibility to enter numbers with non-fixed number of digits after the decimal separator.
The SDK sample DynamicFormatString demonstrates such behavior.

Here is a link to it = > https://github.com/telerik/xaml-sdk/tree/master/MaskedInput/DynamicFormatString

We are marking this feature request as Declined - we won't introduce built-in logic for it. 

Currently, performing consecutively paste operation does not work like in TextBox. In TextBox the strings are concatenated but in MaskedTextInput the caret is in the beggining and only the first paste is successful. 

Provide a way to set .5 and display it like 0.5 , not 5.0 in No-Mask Numeric input.

Supporting DateTimeOffset for DateTime masks

When using German Culture, NoMask and FormatString = "n0" , an incorrect input is produced.

For example pressing 4 times "6" will produce a Value of 7.

This is a parsing issue (6666 becomes 6.666 where "." is a grouping symbol in German Culture).

Then 6.666 is parsed with rounding to 7.

Currently the MaskedInput controls cannot handle properly Chinese input symbols from Google Pinyin or MS IME.

MaskedInput's code relies on methods from TextBox which do not fire when the input is not from keyboard.

Currrently the default ContextMenu of the TextBox inside the MaskedInput is used. You have to set it to null in code behind and the create custom ContextMenu in XAML / Code behind to use it successsfully.

In the Currency and NumericInput controls, clear the sign of the value on SelectAll in order to allow the user to enter a negative value again. At the moment when everything in the controls is selected, the minus key only toggles the sign of the value. Instead you should be able to select a negative value and replace it with another negative value by entering the minus key and the new value.

MinusKeyCustomizations demo is added in our SDK: https://github.com/telerik/xaml-sdk/tree/master/MaskedInput/MinusKeyCustomizations 

Change the InputBehavior when deleting digits after the decimal symbol: For example if the cursor position is marked with '|': Enter: 1234,56|78  (press 'del') Result: 1234,560|8 - change this behavior so that the result can be 1234,56|8.

=====

We can split the request into 2 desired results. Input: 1234.56|78. Pressing Delete

1) Produces Value 1234.5680 but NOT 1234.5608

Solution: Can be achieved with using No-Mask, FormatString and overriding MaskedNumeric/Currency Input and the protected method ReplaceChar. This is demonstrated in the attached sample.

2) (1) is True + Last zero is removed => 1234.568 but NOT 1234.5680

Solution: 2 is tightly coupled with changing the FormatString or Mask dynamically. There is no way to see number 123.456 if the Mask is "x.4" or the Mask is "" + format string is "n4". To see 3 digits only after the decimal point you need to change the Mask to "x.3" or the FormatString (in no-masked scenario) to "n3". This cannot be built-in feature because it changes a public property set by the client. So, this is custom behavior, it is also demonstrated in the SDK demo DynamicFormatString (it is pushed in GitHub with Q2 2014 Release)

Support entering a single digit in a DateTimeMaskedInput control with Mask="MM"

In MaskedTextInput, users need to enter from right to left just like in NumericInput and CurrencyInput.

Allow entering an input in (exponent) scientific notation form for the RadMaskedNumericInput control

Implement a behavior to allow dymanically changing the FormatString precision specifier
=====
Reason to mark it Completed: Added the "Dynamic Format String" sample in SDK. Will be live with Q2 2014 (mid June)

Add a property to force only allowing uppercase values, without needing to specify a number of characters or have the underline in the control.

 

This is achievable in code, but it seems unnecessary to go to such lengths for each instance where it is needed.

 

private void bankCode_ValueChanging(object sender, Telerik.Windows.Controls.MaskedInput.RadMaskedInputValueChangingEventArgs e)
        {
            if (e.NewValue == null)
                return;

            string newValue = e.NewValue.ToString();
            if (newValue.Length > 0)
            {
                newValue = newValue.ToUpper();
            }
            this.txtBankCode.ValueChanging -= this.bankCode_ValueChanging;
            this.txtBankCode.Value = newValue;
            this.txtBankCode.ValueChanging += this.bankCode_ValueChanging;
        }

Currently, the SpinMode logic tries to kick-in on MouseWheel, even if the control is not focused. This handles the event which causes unexpected behaviors in some cases. Do not handle the MouseWheel event when the focus is not within the masked input control. You can consider adding a mode that allows you disable the default behavior.

MaskedInput's Value is bound to property of an Entity class. This property has EditableAttribute.

MaskedInput's will set IsReadOnly True if the EditableAttribute's AllowEdit is False.

Clients need mechanism to stop this validation in MaskedInput.

Initially, when the value is 0, the mask control could look like - $__,___.00 instead of $__,___0.00.

ValueMode feature is designed to format the resulting Value with /without literals and placeholders, depending on the values of all properties - Mask, Value, ValueMode, Placeholder.
This feature request should allow the initial value which user can set or bind, to already include literals placeholders. This way control should display , for example incomplete phone numbers:
For example: Mask ="###-####"
                        ValueMode=IncludeLiteralsAndPlacehodlers
                        Value="___-6789"
Control UI on load: "___-6789".
Currently the control will display "678-9___" in this scenario.