Quick follow-up question:
Since we are storing the state of the item renderer in a property of
the data object, which event would be best used to make sure the
state is restored when the specific item comes back into view?
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: [email protected]
[mailto:[EMAIL PROTECTED] On Behalf Of Jurgen Beck
Sent: Thursday, October 18, 2007 11:14 AM
To: [email protected]
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
