I found a solution to the problem.
If you are over-ride the events then be sure to queue the base events in
order to maintain the state. At the end of your onselectedindexchange event
add the following lines:
if (event.oldTreeNodeIndex != event.newTreeNodeIndex)
tree.queueEvent('onselectedindexchange', event.oldTreeNodeIndex + ',' +
event.newTreeNodeIndex);
Upon next server re-post the state is preserved.
"Graeme Coutts" wrote:
> I dont understand what you mean by 'you need to save the changes'. Im not
> making any changes in the client-side - simply reading the selected node text
> and writing this to another text field.
>
> ""Mohamed El Ashmawy"" wrote:
>
> > You need to save the changes that you made on the client side and re-apply
> > them on post on the server side.
> > Thus, when the tree is rendered again after its post back, it'll be in a
> > state similar to the one before the postback
> >
> > Regards
> > Mohamed El Ashmawy
> > MEA Developer Support Center
> > ITWorx on behalf of Microsoft EMEA GTSC
> >
> >
|