Actually that didn't fix it either, I then had the strange situation of two of the children showing at the same time in the viewstack.
The (hopefully final) fix I have now is to not have the Viewstack be the root component in my custom component, now I have a Canvas as the root in the custom component. Although this is a pointless container in my case it does seem to fix the issue and even meant I could revert to the binding I was first attempting to use. To me this looks like there could be an issue with using a Viewstack as the root of a custom component in some situations. -D --- In [email protected], "dave_defusion" <[EMAIL PROTECTED]> wrote: > > So my fix is as follows: > > 1. Remove the binding > 2. In commit properties: > > if( this.initialized ) { > this.selectedIndex = this._displaySection; > } > > 3. In creation complete handler add call to invalidateProperties();
