Yeah I sort of thought that might be the issue. I have done something similar to your suggestion, though I have had to use a couple of binding tags on the form rather than directly binding the properties becuase in this particular case the sequence of the bindings executing was significant which was the original reason for having them sequential rather than parralel.
The binding tags enable me to control the sequence of execution, they execute in the reverse order to how they are in the mxml. --- In [email protected], Ken Dunnington <ken.dunning...@...> wrote: > > 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; > > <mx:Text id="componentA" text="{someProperty}" /> > <mx:Text id="componentB" text="{someProperty}" /> > <mx:TextInput id="form1" change="someProperty = form1.text" /> > > On Wed, Mar 25, 2009 at 10:19 PM, reflexactions <reflexacti...@...>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? > > > > > > >
