Thank you all.
...to an extent, the repeater brings the functionality in place.
here is the code:
?xml version=1.0?
mx:Application xmlns:mx=http://www.adobe.com/2006/mxml;
mx:Script
![CDATA[
import mx.collections.ArrayCollection;
[Bindable]
Tom and Tracy both have good suggestions. However, I'd recommend using
any of the List based controls, with an itemRenderer, instead of using a
repeater. Unlike the Repeater component, which instantiates all objects
that are repeated (no recycling), the List based controls instantiate
only
Wanted to clarify that when I say (no recycling), I'm refering to
itemRenderer reuse with the same set of data. The recycleChildren
property of a Rpeater does allow for the re-use of children; when a new
data is used.
-TH
In flexcoders@yahoogroups.com, Tim Hoff [EMAIL PROTECTED] wrote:
Tom
--- In flexcoders@yahoogroups.com, Tim Hoff [EMAIL PROTECTED] wrote:
Tom and Tracy both have good suggestions. However, I'd recommend
using
any of the List based controls, with an itemRenderer, instead of
using a
repeater. Unlike the Repeater component, which instantiates all
objects
Absolutely Amy,
Or if you know that the number items will always be performance
acceptable, put your list in a container and set the height of the list
to measuredHeightOfItems; to ensure smooth scrolling by instantiating
all of the items like a repeater. No right or wrong; just depends.
-TH
5 matches
Mail list logo
