--- In flexcoders@yahoogroups.com, "Jason" wrote:
>
>
> > I'd have to test it to know for sure, but I was just theorizing
on why
> > you were not able to access the id array for the image. I could
> further
> > theorize that the image tag, being a child of the repeated
container,
> is
> > tr
> I'd have to test it to know for sure, but I was just theorizing on why
> you were not able to access the id array for the image. I could
further
> theorize that the image tag, being a child of the repeated container,
is
> treated differently by Repeater than the container, but that is
> theor
PM
To: flexcoders@yahoogroups.com
Subject: [flexcoders] Re: Repeaters and Referencing Component IDs
--- In flexcoders@yahoogroups.com <mailto:flexcoders%40yahoogroups.com>
, "Tracy Spratt" wrote:
> I don't know that repeater makes a reference array for child
components
> of
--- In flexcoders@yahoogroups.com, "Tracy Spratt" wrote:
> I don't know that repeater makes a reference array for child
components
> of the repeated parent. It may, but I never do it that way.
OK, because you just said,
>>Repeater would
>>make an
> array of the 5 instances.
How is that fu
width available
From: flexcoders@yahoogroups.com [mailto:flexcod...@yahoogroups.com] On
Behalf Of Jason
Sent: Thursday, February 19, 2009 4:13 PM
To: flexcoders@yahoogroups.com
Subject: [flexcoders] Re: Repeaters and Referencing Component IDs
--- In flexc
--- In flexcoders@yahoogroups.com, "Tracy Spratt" wrote:
>
> The first thing I would do is crate a custom component that
encapsulates
> the repeated UI(tree and image), and repeat that. Then I would
create a
> setter for the image source (set imageSource()) in the repeated
> component.
>
>
>
6 matches
Mail list logo
