Hello !
In our project I am considering using your Treeview component in several places. (for different purposes) as I like the functionality it provides. However there is one issue I need input/help on.
When using your Treeview in a Master/Content page context where the treeview component resides in the masterpage and navigates the user to different aspx pages (A very typical scenario IMO), you would loose the viewstate (because the page navigation is a GET not a POST) which would case the treeiview to loose its state each time I navigate in it. Obviously I want the treeview to keep its state between GET's (and not only postbacks which is easy enough).
Any suggestions for solving this case ? I have seen that Gaiaware treeview can persist state in cookies, is there any similar functionality on this treeview component to keep client state between GETS ?
I guess I could use page_load to find the node being loaded (finding the current node by comparing the navigation attribute of the page requested URL and then selecting it server side ?) but is this how it' supposed to be done.
Thanks, Johan
In our project I am considering using your Treeview component in several places. (for different purposes) as I like the functionality it provides. However there is one issue I need input/help on.
When using your Treeview in a Master/Content page context where the treeview component resides in the masterpage and navigates the user to different aspx pages (A very typical scenario IMO), you would loose the viewstate (because the page navigation is a GET not a POST) which would case the treeiview to loose its state each time I navigate in it. Obviously I want the treeview to keep its state between GET's (and not only postbacks which is easy enough).
Any suggestions for solving this case ? I have seen that Gaiaware treeview can persist state in cookies, is there any similar functionality on this treeview component to keep client state between GETS ?
I guess I could use page_load to find the node being loaded (finding the current node by comparing the navigation attribute of the page requested URL and then selecting it server side ?) but is this how it' supposed to be done.
Thanks, Johan