: Wednesday, October 15, 2008 11:36 PM
To: flexcoders@yahoogroups.com
Subject: [flexcoders] Re: Efficiency and objects in the display list
--- In flexcoders@yahoogroups.com mailto:flexcoders%40yahoogroups.com
, Tracy Spratt [EMAIL PROTECTED] wrote:
Container children must be UIComponents. You will need
:* Wednesday, October 15, 2008 11:36 PM
*To:* flexcoders@yahoogroups.com
*Subject:* [flexcoders] Re: Efficiency and objects in the display list
--- In flexcoders@yahoogroups.com flexcoders%40yahoogroups.com, Tracy
Spratt [EMAIL PROTECTED] wrote:
Container children must be UIComponents. You
@yahoogroups.com [mailto:[EMAIL PROTECTED] *On
Behalf Of *Amy
*Sent:* Wednesday, October 15, 2008 11:36 PM
*To:* flexcoders@yahoogroups.com
*Subject:* [flexcoders] Re: Efficiency and objects in the display list
--- In flexcoders@yahoogroups.com flexcoders%40yahoogroups.com, Tracy
Spratt
Of Amy
Sent: Wednesday, October 15, 2008 11:36 PM
To: flexcoders@yahoogroups.com
Subject: [flexcoders] Re: Efficiency and objects in the display list
--- In flexcoders@yahoogroups.commailto:flexcoders%40yahoogroups.com, Tracy
Spratt [EMAIL PROTECTED] wrote:
Container children must be UIComponents
, October 16, 2008 11:07 AM
To: flexcoders@yahoogroups.com
Subject: RE: [flexcoders] Re: Efficiency and objects in the display
list
I think that is correct. Quoting Alex, “Navigator children must be
Containers, Container children must be IUIComponents, and
UIComponent children can be anything
I've also tried making the components UIComponent based instead of
using Canvas (as I believe it's a little more lightweight) but it
doesn't seem to make a huge difference.
I'd have one UIComponent-derived object (Canvas would be fine) as the
parent, and have your 50-60 dynamic objects be
6 matches
Mail list logo