Bindings do a lot of checking to try and prevent getting stuck in infinite
loops, perhaps that's causing your issue? You might instead try using a
property on the parent component that your sub components bind to, i.e.
[Bindable] private var someProperty:String;
On Wed, Mar 25, 2009 at 10:19 PM, reflexactions wrote:
> In a form I have component1/propertyA bound to component2/propertyA
> which is bound to form1/propertyB.
>
> What I expcted to happen is I set propertyB which triggers to binding to
> set propertyA on component2 which then triggers the binding to set property
> A on component1.
>
> What actually happens is I set propertyB it triggers the binding to set
> propertyA on component2 and it stops there. component1 never gets triggered.
>
> I have used default events simply marking the properties [Bindable], I have
> also tried using custom events and whenI dispatch the change event in
> component2 nothing happens, component1 never gets trigged.
>
> Any thoughts on why?
>
> Does binding ignore events whilst it is setting a property?
>
>
>
