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
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/
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
I'm documenting this here for others who may be struggling with this:
It has been suggested to use a VBox and simply just add children to
it based on items in the dataprovider. That's a great approach and
would have been my workaround. However, Alex was giving enough
pointers to implement
4 matches
Mail list logo
