[flexcoders] Re: unable to bind to property warnings binding to read-only properties

2008-05-21 Thread Doug Lowder
Yes, sorry for the confusion. That should have been: creationComplete=event.currentTarget.someProperty=foo.bar --- In flexcoders@yahoogroups.com, Gordon Smith [EMAIL PROTECTED] wrote: We don't recommend putting curly braces around the values of event attributes like creationComplete... that

[flexcoders] Re: unable to bind to property warnings binding to read-only properties

2008-05-20 Thread Doug Lowder
Binding has a lot of associated overhead and doesn't really serve any purpose when it's a value you know is never going to change. Somehting like the following works well for me. someProperty={foo.bar} becomes: creationComplete={event.currentTarget.somePorperty=foo.bar} --- In

RE: [flexcoders] Re: unable to bind to property warnings binding to read-only properties

2008-05-20 Thread Gordon Smith
We don't recommend putting curly braces around the values of event attributes like creationComplete... that makes it look like databinding even though it isn't. Gordon Smith Adobe Flex SDK Team From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On

Re: [flexcoders] Re: unable to bind to property warnings binding to read-only properties

2008-05-20 Thread Troy Gilbert
We don't recommend putting curly braces around the values of event attributes like creationComplete... that makes it look like databinding even though it isn't. And to finish Gordon's thought: event attributes are already interpreted by the compiler as AS code, not values, so they're