Hey Daniel, I posted about this a while back. See my post "States - add/remove vs create/destroy". I didn't hear a peep from anyone. I'm not sure if it's something that is natively supported by the framework. I don't think so, but I could be wrong. The closest thing I found was the creationPolicy property. Setting that to NONE will get you about an eighth of the way there. I started to write TransientAddChild and TransientRemoveChild classes that extend their mx counterparts, AddChild and RemoveChild but I aborted mission halfway through and chose not to deal with it at this point -- for better or worse.
I definitely still think it is a valid concern and would like to eventually have a solution. best, Paul Daniel Wabyick wrote: > Is there some way to have objects that were added using <mx:AddChild /> > completely destroyed instead of just removed from the DisplayList? > > > The reason for this is that my added panels are bound into a data model > and may end up performing computationally expensive tasks when they > aren't visible. Ideally I would like to completely destroy the component. > > Is this possible with the current API, or does it require some fancy > footwork? > > Thanks, > -Daniel > > -- Flexcoders Mailing List FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com Yahoo! Groups Links <*> To visit your group on the web, go to: http://standraise.corp.yahoo.com/group/flexcoders/ <*> Your email settings: Individual Email | Traditional <*> To change settings online go to: http://standraise.corp.yahoo.com/group/flexcoders/join (Yahoo! ID required) <*> To change settings via email: mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
