Hi,
in my app, I sometimes have to reload an unbound treeview because the underlying data changes. Now it would be nice to keep the state of the tree view (selected nodes, expanded state etc.) What's a good strategy to implement this?
I do have object identity information in an object in the Tag attribute, so I can find the logically identical nodes after a reload.
Thinking of maintaining maps of selected and expanded nodes so I can re-apply those attributes after reload. Is that a good idea?
I'm using demand loading for non-root nodes. Also I have to take into account, that there might be some nodes missing or additional nodes appearing at reload.
Has anybody implemented something similar?
Regards
Erwin
in my app, I sometimes have to reload an unbound treeview because the underlying data changes. Now it would be nice to keep the state of the tree view (selected nodes, expanded state etc.) What's a good strategy to implement this?
I do have object identity information in an object in the Tag attribute, so I can find the logically identical nodes after a reload.
Thinking of maintaining maps of selected and expanded nodes so I can re-apply those attributes after reload. Is that a good idea?
I'm using demand loading for non-root nodes. Also I have to take into account, that there might be some nodes missing or additional nodes appearing at reload.
Has anybody implemented something similar?
Regards
Erwin