--- In [email protected], "Dan Vega" <danv...@...> wrote: > > I would rather take that approach because there can be an infinite number of > children and I want it to be fast. Thats why Ithink loading when requested > is better for this scenario. How can I tell the tree to refresh its view?
The approach I described actually will appear faster to the user than what you're doing, though it can be kind of a pain handling all the synchronization of events. I haven't worked with trees before, but I suspect you'll need to wait for the result to come back and call openNode again (once it knows what's in the node). HTH; Amy
