Hi, No, use it if you need children.
If you think about it, a skin is a Shape. You use the graphics API the renderer it. Or a skin is a class (either embedded graphic or shape) The majority of skins will fall into those two categories. When you need children for a specialized skin, create a subclass of UIComponent or FlexSprite. The performance it is not all that much considering that needing children in a skin doesn't happen that often. Simply put, skins generally need a graphics object and that is it. You can see why Adobe decided to do tricks with the background image, since the HaloBorder is used everywhere and using a UIComponent would create performance issues. Instead they just attach it backwards to the parent. Peace, Mike On 7/16/07, reflexactions <[EMAIL PROTECTED]> wrote:
I am trying to get a better understand of the nuts and bolts of flex so this question should be taken in that light. ProgammaticSkin extends Shape rather than Sprite, one effect of that is that it cant have any children. I assume that this is a resource related issue but is the difference between Shape and Sprite really so great that a Sprite based skin is a real nono?? Thanks
-- Teoti Graphix http://www.teotigraphix.com Blog - Flex2Components http://www.flex2components.com You can find more by solving the problem then by 'asking the question'.
