I wonder if somebody could help clarify something about the persistence behaviour I should be expecting from the RadTreeView's EnableViewState property? I am not sure if I am seeing the behaviour by design or not ...
I have a RadTreeView control which does not appear to maintain its node display arrangement after a postback, in that if the user expands a node, after postback the node has been collapsed once more. Also, when it comes to the underlying datasource bindings etc of the RadTreeView control, it seems as though the control does not persist the Datasource property, for example, that is configured when the control first loads on the initial post of the page. For example, the RadTreeView in question binds to a hierarchical datasource object, but I am having to reconfigure the RadTreeView to a datasource object after each postback, which seems a little counter-intuitive, and a bit of an inefficiency that I would expect the RadTreeView control to avoid by maintaining the state of the datasource object. Perhaps the data configuration and hierarchy display changes would need to be made manually with a Session object instead?
However, I would be interested to know if this is the correct way to go about this issue, or whether I am missing something of importance.
Thanks very much for any advise!