RadMaskedTextInput Value vs Text

[Vit100]

Hi Guys.
I used RadMaskedTextInput with ver. 2011.3.1220.1040 like this
<telerik:RadMaskedTextInput   Text="{Binding BillingFilter, Mode=TwoWay}"  >
Everything worked fine. (I don't remember where I took from that i needed use Text property.)

Unfortunately I have to rolled back telerik libs to old vers 2011.1.04.19.1040 ( due to ....well a lot of reasons..)
Now project is building successfully but throws exception at run time - it complains that Text property is read only. See attached picture

Ok, I decided to be a wise guy and checked documentation -)).
OK I am supposed to use property Value, not Text, like this: <telerik:RadMaskedTextInput Value="{Binding BillingFilter, Mode=TwoWay}" >
Looks like property Text was added recently, this property doesn't exist in  old ver. 2011.1.04.19.1040.
 

How come that old ver. 2011.1.04.19.1040  can be compiled with property added recently?
And what is purpose of property Text?

[Tina Stancheva]

Hi Vitaliy,

The RadMaskedInput controls have always exposed a Text property. It gets the value displayed in the control when it isn't focused (read more). The value of this property depends on the TextMode enumeration, that exposes the following values:

• MaskedText - if a RadMaskedInput control's TextMode property is set to MaskedText, its Text value represents the formatted Value including the placeholder characters.
• PlainText- if a RadMaskedInput control's TextMode property is set to PlainText, its Text value will hold the formatted Value but without the placeholder characters.

However, in the Q1 SP1 release(2011.1.0419.1040) the Text property was still read-only as it was designed to only get the displayed value and form it based on the Value property. However based on our users feedback we decided to allow two-way binding to the formatted value controlled by the Text property. This feature request was added in our PITS in April, 2011 and the feature was implemented in one of the internal builds in May, 2011. This is why the first official release in which the Text property supports binding is Q2 2011 - 2011.2.0712.1040. And this is the reason why with the Q1 SP1 release you can't implement a two-way binding on the Text property.

Regards,
Tina Stancheva
the Telerik team

[Vit100]

Thanks Tina,
Can you (Telerik) add release history for controls in documentation?

It is very difficult to monitor PITS updates and all forum requests, etc...

I think it would be much easier for everyone if you add section for each control somewhere (at the bottom for example) describing all changes. Probably it would be even better if there was ability to subscribe for release notes/changes in text. Then everytime something changed we (users) can see when, and what.. and for critical controls (controls receiving updates offten) users will get e-mail notifications...
Similar to SharePoint subscribtion for changes..

[Tina Stancheva]

Hi Vitaliy,

Thank you for this feedback. We already added a Changes and Backward Compatibility page in our documentation where we will describe any breaking changes. And we also provide a Release History that lists all items that are fixed/added in the release.

And as I can see your point on the matter I want to assure you that we will definately keep discussing how to further fascilitate our customers efforts in keeping track of the RadControls development.

All the best,
Tina Stancheva
the Telerik team

[Vit100]

It is true, that some controls have Changes and Backward Compatibility section.

I mean that it better to have release notes history with control in same place together.
Thank you anyway.