Thank you for your patience.
control inherits from the native TextBox
control and we don't have control over the events that come from the native component. The first time TextChanged
gets fired is the expected occasion when the text is changed. The second time is caused by the fact that we have another TextBox
's template which is used for the view of RadTextBox
is true and when IsEnabled
is false. The second TextBox
property also changes since its data bound to the same value and also fires the TextChanged
event which gets escalated to RadTextBox
The second issue is related to the fact that the binding gets evaluated only when the control loses focus. Since the initial value is empty, you always see that the value of Address1
is null. If you change the text, move the focus and get back to change the text again, you will see that the value of Address1
will not be null any more, but it will be the value of the text as it was when the control lost focus. Please note that this behavior is observed with the native TextBox
control as well.
You can have a look at these two forum posts: here
. They both discuss options for applying validation without using code-behind.
Don't hesitate to write us back if you need further assistance.
TRY TELERIK'S NEWEST PRODUCT - EQATEC APPLICATION ANALYTICS for WINDOWS PHONE 7.
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 >>