As I understand it, Repeater is not anywhere nearly as tightly
integrated with the framework as an item renderer.  I do not think any
methods are called by the framework.  I always do as you have done, and
explicitly pass a reference to the currentItem into the repeated
component.

 

I think of Repeater as  a way to save myself a lot of manual addChild()
/ removeChild() logic.

 

The only framework integration I can think of is the ability to specify
whether the child instances are recycled using recycleChildren="true".
My expectation is that this sipps the removeChild() stuff and just
re-populates the properties.

 

Tracy

 

________________________________

From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On
Behalf Of simonjpalmer
Sent: Saturday, November 03, 2007 12:15 PM
To: flexcoders@yahoogroups.com
Subject: [flexcoders] Re: Repeaters and ListCollectionViews

 

Yup, got it working, however it seemed to need me to explicitly bind a
property of the Repeater to the control being repeated before it
started working. 

<mx:Repeater dataProvider="{filtered_planpoints}" id="pp_repeater">
<crm:ctrl_PlanPointDropTarget width="100%"
activePlanPoint="{pp_repeater.currentItem}"
idx="{pp_repeater.currentIndex}"/>
</mx:Repeater>

it wasn't until I added 

activePlanPoint="{pp_repeater.currentItem}" 

that it started working. I originally was overriding the set data()
method on the control expecting to be given the appropriate object
from the data array so I could initialise my control and had no
reference from the drop taregte control and the repeater.

If I get rid of the explicit references to the repeater it stops
working.

Simon

--- In flexcoders@yahoogroups.com <mailto:flexcoders%40yahoogroups.com>
, "simonjpalmer" <[EMAIL PROTECTED]>
wrote:
>
> Is it possible to use a ListCollectionView as the dataProvider for a
> Repeater?
> 
> I think the answer is no because I can't get it to work, but I wanted
> to make sure that it is not just me writing buggy code.
> 
> Thanks
> Simon
>

 

Reply via email to