Thanks Tracey this is what I'd discovered.
I hadn't realised that:
mx:whatever dataProvider={arrDataSource} /
is different to:
function setSomething()
{
myComponent.dataProvider = arrDataSource
}
So I'm assuming that basically the {} in mxml does all the event wiring to
actually Bind the
...My ArrayCollection is really only going to be set once... Don't
bind. Set the dataProvider explicitly.
Tracy
From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On
Behalf Of DannyT
Sent: Tuesday, March 11, 2008 5:15 AM
To:
Nevermind, I just found a past post from
Matt saying databinding can only be done from MXML right now and not
programmatically. Sorry for the post!
robert l. brueckmann
senior web developer
merlin securities
595 madison avenue
new york,ny 10022
p: 212.822.4821
f: 212.822.4820
Its probably because of the way
they are instantiated. dispatchEvent() is a mix-in from UIEventDispatcher.
You might try adding ChangeEvent to the
component once it is created. Just a thought.
Hey, Im at 11 Madison Ave.
Regards,
Rob Rusher
RIA Consultant
Macromedia
Hi,
Databinding is a special beast in flex, and is set up in mxml-as compiling
The compiler needs the metadata to figure out what events it has to
listen to for each property (or perhaps just use getters setters). It
then sets up a complex mechanism of watchers and stuff to make binding
happen.
Bucchi
Sent: Tuesday, August 02, 2005 6:16 PM
To: flexcoders@yahoogroups.com
Subject: Re: [flexcoders] databinding question
Hi,
Databinding is a special beast in flex, and is set up in mxml-as compiling
The compiler needs the metadata to figure out what events it has to
listen to for each property
6 matches
Mail list logo
