Hello,
I've come across a strange issue I can't seem to get my head around:
I currently have a Dynamic TabStrip/MultiPageView setup going, which dynamically load controls as tabs are added. I have been replacing the regular ASP TextBox controls with RadTextBox controls, however I have noticed that upon changing tabs back and forth, all information in the RadTextBox controls are erased, while the ASP TextBox controls all stay filled in. I'm curious as to what the difference with the TextBoxes are that might be causing this.
It's a little tricky to get workable code to reproduce this, but from what I can tell changes are lost on any postbacks (placing a RadTextBox outside my tabstrip to test also causes information to be lost)
While I would normally assume this is all due to my lack of understanding of ASP page cycles, the fact that I get the expected behavior with an ASP box but not with a RAD box is confusing. Any help in the right direction or even what I can do to try and isolate the problem would be greatly appreciated.
Thank you.
EDIT:
I've narrowed this down to find that Loading a control seems to break the persistence (although it doesn't seem to matter whether the text boxes are in the control our outside the tabstrip completely - the same thing happens). My understanding is that the ViewState/Postback shouldn't affect text boxes (and they don't affect the regular ones) as per this article here. So on the loading of a control, what's destroying the changes in the RadTextBox, but not destroying the changes in the ASP TextBox?
I've come across a strange issue I can't seem to get my head around:
I currently have a Dynamic TabStrip/MultiPageView setup going, which dynamically load controls as tabs are added. I have been replacing the regular ASP TextBox controls with RadTextBox controls, however I have noticed that upon changing tabs back and forth, all information in the RadTextBox controls are erased, while the ASP TextBox controls all stay filled in. I'm curious as to what the difference with the TextBoxes are that might be causing this.
It's a little tricky to get workable code to reproduce this, but from what I can tell changes are lost on any postbacks (placing a RadTextBox outside my tabstrip to test also causes information to be lost)
While I would normally assume this is all due to my lack of understanding of ASP page cycles, the fact that I get the expected behavior with an ASP box but not with a RAD box is confusing. Any help in the right direction or even what I can do to try and isolate the problem would be greatly appreciated.
Thank you.
EDIT:
I've narrowed this down to find that Loading a control seems to break the persistence (although it doesn't seem to matter whether the text boxes are in the control our outside the tabstrip completely - the same thing happens). My understanding is that the ViewState/Postback shouldn't affect text boxes (and they don't affect the regular ones) as per this article here. So on the loading of a control, what's destroying the changes in the RadTextBox, but not destroying the changes in the ASP TextBox?