Yeah, that's the conclusion I've come up with as well. After looking at the "expandItem" funciton in Tree.as I'm convinced this would be a pretty difficult patch.
It seems to me that if each branch were a list in it's own container, this wouldn't be so hard, but I understand that would probably add additional overall tree management issues. The frustrating thing is that I did this in AS2 with some container and array management. http://www.useflashmore.com/accordion-menu-example/ <http://www.useflashmore.com/accordion-menu-example/> I really wanted to create a reusable flex control that would have the same functionality. >From a usability perspective everything works/behaves really nice for the first couple of levels. If there are more than 3 or 4 levels though I could see view getting a bit smooshed. I did get around this issue for the most part in the past by setting a rule that only one branch could be open at any given time. Can you think of any other way to create a reusable component like this without extending the tree and without rewriting the complete tree/menu/list functionality from scratch?
