I had the same issue with the player on Shilliber.com. Exact same use case. I think the guy who programmed it up ended up using a VBox.
Juan scalenine.com | degarafa.com | ocflex.org --- In flexcoders@yahoogroups.com, Jurgen Beck <[EMAIL PROTECTED]> wrote: > > Makes sense, Alex. Thanks! > > I also found an entry in the Flex Bug system after I posted on the > list. So, this is for documentation for others to see: > > http://bugs.adobe.com/jira/browse/SDK-12343 > > In it was a great reference to an article you wrote: > > http://blogs.adobe.com/aharui/2007/03/ > thinking_about_item_renderers_1.html > > On Oct 18, 2007, at 1:47 PM, Alex Harui wrote: > > > > > Renderers are recycled. Only as many renderers that you can see > > are created regardless of how many items in your data provider. > > So, one renderer can end up having to render various items in the > > dataprovider. As such, all aspects of its visuals must be driven > > by the .data object including which state it is in. > > > > > > > > From: flexcoders@yahoogroups.com > > [mailto:[EMAIL PROTECTED] On Behalf Of Jurgen Beck > > Sent: Thursday, October 18, 2007 11:14 AM > > To: flexcoders@yahoogroups.com > > Subject: [flexcoders] List Component: Working with Collapsed and > > Expanded ItemRenderer > > > > > > > > I am experiencing something mildly strange with the List component > > when using a custom item renderer that has two states, a collapsed > > state and an expanded state. > > > > When I have one or more item renderers in the expanded state, the > > List component eventually will display the vertical scrollbar. Here > > is the strange part: > > > > When using the scrollbar to scroll through the list, the original > > expanded item renderers that would normally disappear with their > > expanded state from the visual range of the list get collapsed and > > new list items that have not been expanded do so in their place. > > > > As I am not forcing this behavior my thinking is that the List > > component is either missing a property setting to prevent this > > behavior, or this may be either a bug, or simply by design. > > > > Anyone with some more info on this? > > > > Thanks, > > > > Jurgen > > > > > > > > >