There's two things to keep in mind when pondering bindings:
1) Bindings work on "property chains", using chains of ChangeWatcher
instances. It's only a couple of pages of code, and pretty easy to get your
head around. You're right that they simply "stop" when they get to a null,
and return null.
2) Everything inside your "{}" when you bind in MXML goes into a function,
which is called wrapped inside a try{}/catch{}, and exceptions that are
thrown by it are simply ignored.
-Josh
On Mon, Dec 1, 2008 at 2:33 AM, Dave Kong <[EMAIL PROTECTED]> wrote:
> I dont know any docs, but I think it happened to me a couple of times and
> the result is that the databinding simply does not fire for any changes
> after the null in the chain.
>
> Do a simple test app and try it out. it will be faster than you looking for
> the doc.
>
>
> On Fri, Nov 28, 2008 at 12:01 PM, Michael Prescott <
> [EMAIL PROTECTED]> wrote:
>
>> Is there any reference material that describes how Flex behaves when it
>> encounters a null part way along a data binding chain?
>>
>> Michael
>>
>
>
>
--
"Therefore, send not to know For whom the bell tolls. It tolls for thee."
Like the cut of my jib? Check out my Flex blog!
:: Josh 'G-Funk' McDonald
:: 0437 221 380 :: [EMAIL PROTECTED]
:: http://flex.joshmcdonald.info/
:: http://twitter.com/sophistifunk
