ListItemRenderer
-Original Message-
From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On
Behalf Of Tom Chiverton
Sent: Wednesday, October 03, 2007 1:47 AM
To: flexcoders@yahoogroups.com
Subject: Re: [flexcoders] Re: Force creationComplete with ItemRenderer
On Tuesday 02 Oct
On Tuesday 02 Oct 2007, [EMAIL PROTECTED] wrote:
> I recommend that the data setter just calls invalidateproperties
Is there an example of an 'adobe recommended' renderer that uses this
approach ?
--
Tom Chiverton
Helping to preemptively extend leading-edge appliances
on: http://thefalken.livej
I recommend that the data setter just calls invalidateproperties
-Original Message-
From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On
Behalf Of Tom Chiverton
Sent: Tuesday, October 02, 2007 8:18 AM
To: flexcoders@yahoogroups.com
Subject: Re: [flexcoders] Re: Force
On Tuesday 02 Oct 2007, [EMAIL PROTECTED] wrote:rties().
> What should I put in set data(), and what should I put in
> commitProperties()?
We do it all from set data().
--
Tom Chiverton
Helping to centrally syndicate second-generation market-growth
on: http://thefalken.livejournal.com
*
Tom,
> What a lot of people do is make sure they have an overriden 'set
data' method
> in their renderer that (re)sets up their component for new data.
Could you elaborate on this a bit? In my renderer, I have a set data()
that first calls super.data = value, and then displays its text fields
di
5 matches
Mail list logo