Containers are heavy. They measure their children, think about clipping and scrollbars, compute the size and position of children, think about borders, background colors and more. If you aren't using 80% of those features, then you shouldn't be using a container.
A UIComponent can be easily subclassed to position its children vertically.and won't spend time thinking about those other things. ________________________________ From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of christian.menzinger Sent: Friday, May 30, 2008 9:04 AM To: [email protected] Subject: [flexcoders] Performance issues while creating several instances of DisplayObject at the same Hi there, while experimenting with Containers and UIComponents I received very strange results. Is it possible that the instantiation and rendering of about 150 DisplayObjects can take up to 3 seconds of processing time? I have a very light weight application attached where 20 views (containing a Label and a VBox) and in average 4 child views (containing 2 Labels next to each other) are instantiated and rendered at the same time. The rendering of 1000 native FlashObjects like TextField in a pure AS-Project takes about 95ms(!) to update the display! The performance differs extremely if you don't set any width on the parentViews. Could you please check if I have overseen something or used bad code? It would be great to get a hint how to increase the overall performance. I need a solution which increases rendering performance as much as possible and allows me to use text truncation and dynamic setting of widths. Thanks a lot in advance for everything that could lead me into the right direction. view sample Application (could download source by right clicking) http://www.metadudes.com/samples/flex/performance_issue/LightWeightChild Creation.html <http://www.metadudes.com/samples/flex/performance_issue/LightWeightChil dCreation.html> BR, Chris
