W
William Sullivan
I've got a treeview that i'm filling using PopulateOnDemand (ajax calls).
The TreeNode isn't sealed, so I thought I could extend it (call the new one
SuperTreeNode) and add a bunch of data to the new node that I need to keep
track of. But when the TreeNodePopulate event fires and I get the node from
the TreeNodeEventArgs, it isn't the same node I put in the tree, its an
actual TreeNode that just looks like my SuperTreeNode, minus all my important
data. Is there any way to change this behavior? I suspect the problem lies
in the javascript behind the call, so that leads me to believe that I don't
have much chance to get around it. Would it be better to put my data in a
custom HierarchicalDataSource? And if I do this, will I be able to figure
out which of the datasource's nodes I need to fill from
TreeNodeEventArgs.Node? TIA.
The TreeNode isn't sealed, so I thought I could extend it (call the new one
SuperTreeNode) and add a bunch of data to the new node that I need to keep
track of. But when the TreeNodePopulate event fires and I get the node from
the TreeNodeEventArgs, it isn't the same node I put in the tree, its an
actual TreeNode that just looks like my SuperTreeNode, minus all my important
data. Is there any way to change this behavior? I suspect the problem lies
in the javascript behind the call, so that leads me to believe that I don't
have much chance to get around it. Would it be better to put my data in a
custom HierarchicalDataSource? And if I do this, will I be able to figure
out which of the datasource's nodes I need to fill from
TreeNodeEventArgs.Node? TIA.