It would not be expected if it happens in the same PostBack. But it actually happens on the next one.
Here is an example:
1. Load the page.
2. Type 50 in the PS
3. During the PostBack only txtLeistungPS_TextChanged
will be executed. And in this point text of kW
textbox changes 37
Now you have two options after the page loads, to change the text of kW
or of PS
A. Now after the page loads you change the text of kW
textbox. In this case only txtLeistungkW_TextChanged
will be executed, because you have changed it's text one time on server side, and another time on client side. txtLeistungPS_TextChanged
will not be executed, since it's text was not changed after the previous PostBack.
B. However if you change the text of PS
textbox, then TextChanged of both controls should fire on the next PostBack. This is because text of kW
, was changed on server side the previous time and the text of PS
was changed in the browser.
About your second question, as what I examine here, it is consistent for both TextBoxes.
If you load the page and enter 5
in the kW
and PostBack, the value in PS
got's auto-calculated to 7
. Then if you change the value of kW
and PostBack again, the TextChanged event will be fired for both controls. Because the value of first one was changed from 5
, and the second one from null
. After this auto-calculated value of the PS textbox will become 18
Now difference that you could see is that when you change the value of PS
textbox two times, the second time it will remain the previous value. This happens because the TextChanged
is always fired first (when both events are fired), which cause the value of PS
value to be changed depending on value of kW.
the Telerik team
If you want to get updates on new releases, tips and tricks and sneak peeks at our product labs directly from the developers working on the RadControls for ASP.NET AJAX, subscribe to their blog feed