Barnes
Sent: Monday, October 24, 2005
9:49 PM
To: flexcoders@yahoogroups.com
Subject: Re: [flexcoders] Re:
BindingManager and Properties interogation.. (Flex 1.5)
On 10/25/05, Matt
Chotin [EMAIL PROTECTED]
wrote:
If you want to ensure that the class gets linked but is
available
From: flexcoders@yahoogroups.com [mailto:flexcoders@yahoogroups.com] On Behalf Of Scott
Barnes
Sent: Sunday, October 23, 2005
10:09 PM
To: flexcoders@yahoogroups.com
Subject: [flexcoders] Re:
BindingManager and Properties interogation.. (Flex 1.5)
Just to add more
perspective to this.
I
: flexcoders@yahoogroups.com [mailto:flexcoders@yahoogroups.com] On Behalf Of Scott
Barnes
Sent: Monday, October 24, 2005
4:54 PM
To: flexcoders@yahoogroups.com
Subject: Re: [flexcoders] Re:
BindingManager and Properties interogation.. (Flex 1.5)
Hi Matt,
On 10/25/05, Matt
Chotin [EMAIL
@yahoogroups.com]
On Behalf Of Scott
Barnes
Sent: Monday, October 24, 2005
4:54 PM
To: flexcoders@yahoogroups.com
Subject: Re: [flexcoders] Re:
BindingManager and Properties interogation.. (Flex 1.5)
Hi Matt,
On 10/25/05, Matt
Chotin [EMAIL PROTECTED]
wrote:
Well in this particular example you
, 2005
9:49 PM
To: flexcoders@yahoogroups.com
Subject: Re: [flexcoders] Re:
BindingManager and Properties interogation.. (Flex 1.5)
On 10/25/05, Matt
Chotin [EMAIL PROTECTED]
wrote:
If you want to ensure that the class gets linked but is
available at creation up you can use [ClassReference
Just to add more perspective to this.
I basically want to have the ability to provide an array of some sort,
that will turn off binding for a given property and simply add it to a
containers properties.
At present if you did cellRenderer={ whatever }, that argument
wouldn't show up in
6 matches
Mail list logo
