It depends, but UIComponent doesn't care about clipping, scrollbars, etc.
________________________________ From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of Steve Mathews Sent: Wednesday, January 23, 2008 8:02 AM To: flexcoders@yahoogroups.com Subject: Re: [flexcoders] addChild vs. addRawChild and performance So you are saying that instead of using a Canvas as the container inside of my app, I could just use UIComponent or ScrollControlBase? Any idea of how much performance gain this could be? On 1/22/08, Alex Harui <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> > wrote: It would be best to not use containers and just use UIComponent or ScrollControlBase ________________________________ From: flexcoders@yahoogroups.com <mailto:flexcoders@yahoogroups.com> [mailto:flexcoders@yahoogroups.com <mailto:flexcoders@yahoogroups.com> ] On Behalf Of Steve Mathews Sent: Tuesday, January 22, 2008 12:52 PM To: flexcoders@yahoogroups.com <mailto:flexcoders@yahoogroups.com> Subject: [flexcoders] addChild vs. addRawChild and performance Someone posted recently describing that addRawChild adds DisplayObject in a way that they are not included in the size and layout of the container (if I understood correctly). Does anyone know if this would be better or worse for the overall performance of a Flex app? So if you did not need layout features of the framework, would it be better to add everything as raw children?
