Hi, > caused by a UIComponent that contains several children and it has a dropshadow (C level says we need to have dropshadow so can't remove it).
I can't believe a UIComponent is killing your performance that bad, I would be willing to bet there is something else going on here but without code, I can only speculate. Mike On Fri, Oct 3, 2008 at 9:59 AM, flexaustin <[EMAIL PROTECTED]> wrote: > Is there any benefit (memory/cpu usage) to using Sprite as your base > component over UIComponent? I know if use Sprite in Flex you need to > use IUIComponent then implement all the methods require, which is a > huge pain. > > Or you can use composition and create and instance of a UIComponent > and use that, but then that kind of defeats the purpose of not using > or instantiating an instance of a UIComponent as now you have both a > UIComponent and Sprite. > > The reason I ask is I have a very rendering intensive app that is > dragging my CPU down and its all caused by a UIComponent that contains > several children and it has a dropshadow (C level says we need to have > dropshadow so can't remove it). > > I am thinking I will just need to use UIComponent and move on. > > TIA > > > -- Teoti Graphix, LLC http://www.teotigraphix.com Teoti Graphix Blog http://www.blog.teotigraphix.com You can find more by solving the problem then by 'asking the question'.
