Flex bindable variable not updating dating late in life
But, hang on: Say I have this Model: Notice how my Model is also changing?So, you can see that one-way binding actually ensures that both the source and the destination point to the same object reference.So, these things need to be kept in mind when databinding – whether to use one-way or two-way.
diane keaton and warren beatty dating - Flex bindable variable not updating
So manually overriding a binding destination will not prevent the databinding from re-executing when the source changes – as you’d expect.
Justin, I thought you were seeing the same behavior I was seeing as shown in the code below with XML binding.
And, you can see the Model doesn’t change from this point on, because it still points to the original instance.
If you wanted the Model to update from this change, you would add: I seen two way binding happen when the destination is null…
IF you change a property of either the source or the destination – as you have by calling “append Child” – then both will change, because both src & dest point to the same object.
However, this can lead to confusion, as it has to many people – myself included.
With just one mx binding, changes in src show in the destination and changes in Destination show in src…
I tried the with strings but it does not show the same behavior…
In your case, the following sequence will simulate a two way binding. public var some Name: String; // initialized to null by default I think src and dest refer to the same object, resulting in two way binding – if you pass dest as null….