Yes. To take advantage of the spark architecture you have to extend SkinnableComponent (or one of the other SkinnableXXX classes, depending on your needs).
Example: Creating a skinnable Spark component http://help.adobe.com/en_US/flex/using/WS460ee381960520ad-2811830c121e9107ecb-7feb.html Haykel Ben Jemia Allmas Web & RIA Development http://www.allmas-tn.com On Tue, Sep 6, 2011 at 6:48 PM, Nick Middleweek <n...@middleweek.co.uk>wrote: > ** > > > Thanks for this... So I'm extending UIComponent, does this mean I'm doing > it the MX way? > > Cheers... > > > On 6 September 2011 14:38, Haykel BEN JEMIA <hayke...@gmail.com> wrote: > >> ** >> >> >> Hi Nick, >> >> if you use Spark components and the child components you want to add are >> fixed and known, e.g. a 'close' button that should be visible on mouse-over, >> then I would use skin states and manage visibility of the components in the >> skin. >> >> Haykel Ben Jemia >> >> Allmas >> Web & RIA Development >> http://www.allmas-tn.com >> >> >> >> >> >> On Tue, Sep 6, 2011 at 10:28 AM, Nick Middleweek >> <n...@middleweek.co.uk>wrote: >> >>> ** >>> >>> >>> Hi, >>> >>> I've been trying to find the correct 'place' to create new components >>> after the parent component is UPDATE_COMPLETE. >>> >>> During initialisation, we create child components in *createChildren()*but >>> where/ when should we create them for e.g. in response to a mouseOver or >>> a mouseClick event? >>> >>> Is it simply 'ok' to *this.addChild( *myNewButton *)* in a MOUSE_EVENT >>> function handler or should I be setting some dirty flag to trigger off an >>> invalidation and then add the button in a lifecycle override function? >>> >>> >>> Thanks, >>> Nick >>> >>> >>> -- >>> Sent by Nick Middleweek ( { email: n...@middleweek.co.uk, mobile: +44(0)774 >>> 035 5424 } ); >>> >>> >>> >> > > > -- > Sent by Nick Middleweek ( { email: n...@middleweek.co.uk, mobile: +44(0)774 > 035 5424, blog: http://www.middleweek.co.uk } ); > > > >
