Order of events in TreeView & its DataSource...

[Ken De Vries]

I am curious about the timing of events for the TreeView and the Datasource.

 I am trying to scroll a Treeview control's contents so that the expanded event is scrolled to the top.  I have gotten this to work for the most part.  You can read my solution in another thread.  However, I am seeing the TreeView's Expand event fire before the datasource RequestStart and RequestEnd events.

This order does not seem to make sense.  My scrolling of the treeview's selected node malfunctions periodically because the expand event fires first, before the datasource returns the data for the expanded node.  This results in the scrolling not happening at all sometimes if returning the data takes a while.

Is this design intentional?  If so, is there a way around it?  If Javascript were multi-threaded, I could easily get around this but I cannot seem to come up with a way to get around this problem.

I would like to delay the Expand event until after the datasource RequestEnd event.

Possible?

[Nencho]

Hello Ken,

I am afraid that this behavior is by design. The internal logic behind this is the fact that the DataSource's request for child items is triggered once the parent one is expanded. Otherwise, the control cannot be aware when exactly the request should be fired, unless an user interaction occurs (by expanding certain Item).

Regards,
Nencho
Telerik