Thanks everyone for your help and input. I finally figured it out. I
have a little bit of "egg in my face" ;-), but maybe this will help
someone else avoid the same mistakes..
1. I recently installed Flex Builder on a VISTA machine. Had to copy
a working XP installation as the setup program for Flex will not run on
VISTA. One small detail I missed, I did not get the debug Flash Player
plugin. It is installed by the setup program or you can manually
download it from Adobe. This would also explain why I have not seen any
runtime errors lately ;-) Now that we have that out of the way, some
info on the data binding problems.
2. In my app I have a whole bunch of HTTPService calls to read data
from a backend. One of the first service calls returned XML nodes where
one item had a missing attribute. My assumption has always been that if
you bind to an attribute value (such as @name), and if such attribute is
missing that data binding would either ignore the node, or assume a
blank value (like <tag name="" />). This is NOT the case and data
binding fails.
3. More interesting about this is: Once you have one HTTPService data
binding fail, there is no predicting how many others will fail / be
ignored. It does explain somewhat why subsequent calls to explicit
executeBinding are succesful if the underlying data is sound...
Thanks again...
--- In [email protected], "Tracy Spratt" <[EMAIL PROTECTED]> wrote:
>
> Binding directly to lastResult is hard to debug. I advise using a
> result handler function to set an instance variable, and bind to that.
>
> Tracy
>
>
>
> ________________________________
>
> From: [email protected] [mailto:[EMAIL PROTECTED]
On
> Behalf Of iko_knyphausen
> Sent: Monday, April 02, 2007 1:26 AM
> To: [email protected]
> Subject: [flexcoders] data binding limitations?
>
>
>
> Hello everyone,
>
> I am experiencing some very strange behavior regarding data binding.
> First off, would anyone know why the following XMLListCollection does
> not bind successfully to its source,
>
> <mx:XMLListCollection id="xlcUsers" filterFunction="filterUser"
> source="{xmlSetup.lastResult.USER}"/>
>
> The xmlSetup is a HTTPService that returns a list of user accounts in
> e4x format. The moment I add a binding tag, like the one below, the
> XMLListCollection has all the data I expect.
>
> <mx:Binding destination="xlcUsers.source"
> source="xmlSetup.lastResult.USER" />
>
> I have several XMLListCollections bound to HTTPService results, and I
> never had to create explicit bindings.
>
> The second question is maybe related: Are there limits how many
bindings
> you can have in an application? It seems to me that, as the
application
> grows, and as I am adding more and more databound controls, previously
> succesful databound controls "loose" their bindings silently. They can
> be brought back by explicit calls to "executeBindings" but that sort
of
> defies the purpose of having it done automatically - if you have to be
> explict, you may as well assign values upon change events...
>
> Am I missing something...or does anyone else have similar experiences?
>
> Thanks much
>
> Iko
>
