Tabs control - Ajax Control Toolkit
-
Hi, I'm using the Ajax Control Toolkit, and I have a problem with the Tabs control. On the Control Tollkit description it's written that the selected page should remain enabled after a postback..But it doesn't happens. I'm using Visual Web Developer, and testing the pages using his virtual server. After a postback the selected tab is changed, and is always selected the one who is open in the Web developer page.. Suggestions? Thanks!
-
Hi, I'm using the Ajax Control Toolkit, and I have a problem with the Tabs control. On the Control Tollkit description it's written that the selected page should remain enabled after a postback..But it doesn't happens. I'm using Visual Web Developer, and testing the pages using his virtual server. After a postback the selected tab is changed, and is always selected the one who is open in the Web developer page.. Suggestions? Thanks!
-
Hi, I'm using the Ajax Control Toolkit, and I have a problem with the Tabs control. On the Control Tollkit description it's written that the selected page should remain enabled after a postback..But it doesn't happens. I'm using Visual Web Developer, and testing the pages using his virtual server. After a postback the selected tab is changed, and is always selected the one who is open in the Web developer page.. Suggestions? Thanks!
In the prototype that I tested with, the tab control did retain its value through postbacks, whether I changed tabs by clicking them in the UI or used the client script API to set the tab. The only time that I was able to reproduce the behavior that you are seeing is when I explicitly set the
ActiveTabIndexproperty of the control on the server side. In that case, the index that I requested was honored. Are you setting theActiveTabIndexproperty at all? If so, you may need to ensure that you're only setting it when not in a postback. Hope that helps. :)--Jesse
"... the internet's just a big porn library with some useful articles stuck in." - Rob Rodi
-
In the prototype that I tested with, the tab control did retain its value through postbacks, whether I changed tabs by clicking them in the UI or used the client script API to set the tab. The only time that I was able to reproduce the behavior that you are seeing is when I explicitly set the
ActiveTabIndexproperty of the control on the server side. In that case, the index that I requested was honored. Are you setting theActiveTabIndexproperty at all? If so, you may need to ensure that you're only setting it when not in a postback. Hope that helps. :)--Jesse
"... the internet's just a big porn library with some useful articles stuck in." - Rob Rodi
-
you may need to use if (Page.IsPostBack == true) { do something i.e. set current tab as default } or not use default tab put your code up if you want hope that makes sense
-
no, i'm not using the ActiveTabIndex, I'm just using the tabs without properties at all.. ??
It may be helpful to post some of your code at this point, as I'm unable to reproduce the behavior that you're seeing. Hopefully, that will help us to find the issue.
--Jesse
"... the internet's just a big porn library with some useful articles stuck in." - Rob Rodi
-
It may be helpful to post some of your code at this point, as I'm unable to reproduce the behavior that you're seeing. Hopefully, that will help us to find the issue.
--Jesse
"... the internet's just a big porn library with some useful articles stuck in." - Rob Rodi
The matter is that it' doesn't depend from the code I used.. Every time I create a Tab panel from the Control Toolkit, even in a new page of a new project, the active tab is not preserved after postback. Could it depend from Visual Web Developer?I'm trying to test it with the virtual server of VWD, perhaps it should work if the application is online.. Or not? Is it normal to have it not working if trying from VWD? Thanks!