I'm trying to figure out away to save the expand/collapse states of all the
child nodes in a TreeView across multiple pages. Basically we have a basic
menu on the left side of the page when they navigate to a node that links
them to another page with the same menu stucture, it resets the menu to it's
default state (ie everything is collapsed). I'd like to keep open what the
user opened. I'm thinking maybe I can do this by overriding the
onselectedindexchange method and some how save the expanded properties of
all the nodes in the tree. My other thought is to maybe use multipage views
but that won't always be appropriate. Also I think I could pretty easily
hack out something akin to a bread crumb trail for each of the sub pages,
but I'd like to just save whatever the menu state is for the user and
persist that over all pages. I was using lightweight javascript/css before
but I had the same issue with state management. One other thought is that
When you set autopostback to true it sends everything back to the
originating page, and keeps everything open. Could I maybe use a postback
to process the click then use Sever.redirect(url)? I've been doing alot of
brain storming I just can't seem to come up with anything that works.
Thanks
Brian