Oh yeah, I neglected to mention the details of my install.
I am on Win XP SP3, running Flash Builder 4 Beta2, and build 13099 of the Flex 4 SDK. The project is publishing to AIR (most current non-beta version)
1 person found this helpful
I'd be concerned that when you click on the inner List, that even the outer List will see that click. It might also be that if you alter the dataProvider enough to get the List to display that you get a mouseOut as we change renderers or that selectedIndex gets reset as we change renders.
Is there a reason you can't use mx:Tree with s:MXTreeItemRenderer? Or even the way I modified Spark List to show hierarchical data that is on my blog?
Flex SDK Developer
Adobe Systems Inc.
Yes, I had recently determined that the cause was the selectionChange firing on the outer list.
To answer your question, there really isn't a good reason I can't. When I started learning the Spark architecture, I challenged myself to forego the halo components altogether, and have been building with that in mind.
Its really funny, I was looking at that post on your blog yesterday, and I downloaded the source, and couldn't understand how the thing was built.
So, it looks like I need to do 1 of 2 things.
1. Figure out a way to change the hit area for the List component, or otherwise swallow the selectedIndexChange on the parent List.
2. Re-build using the mx:Tree or figure out how yours works.