Only the viewable nodes can be found within the "flat" list, which is Tree.listItems by the way. Children of collapsed nodes are not present (since they are not viewable). And the length of the list does not match the number of viewable nodes, the list is bigger. It takes some time to figure that out...
dropData is accessible because it is not private --- In [email protected], "grantdotcox" <[EMAIL PROTECTED]> wrote: > > Well, it's the same index, but it certainly isn't the same thing. > Moving an item to be the last in a list in a folder is not the same as > placing it outside of the folder. But they both have the same index > (as the tree list is seen as a flat list as far as index is concerned). > > But thanks for that link - I didn't realise that accessing a private > member would be as simple as: > > public function get dropData():Object{ > return super.mx_internal::_dropData; > } > > Unfortunately that Tree has very flaky drag & drop support with a > small sample array (their example from XML seems fine though). But I > can subclass Tree with just that function above and it should be fine. > > Thanks again. > > > --- In [email protected], "benoit.kogut" <benoit.kogut@> > wrote: > > > > Because trying to drop an item after the last node of a branch is seen > > as trying to drop it outside the branch (actually, right below the > > branch). > > > > The dropData property can be made accessible, check the source of the > > Tree with spring loaded folders. > > > > > http://flexibleexperiments.wordpress.com/2007/02/26/flex-201-tree-with-spring-loaded-folders-update-2/ > > > > > > >
