RE: [flexcoders] Could the Flex Gurus shed some light on this behavior?

[mailto:[EMAIL PROTECTED] On Behalf Of Daniel Gold Sent: Wednesday, April 23, 2008 10:14 AM To: flexcoders@yahoogroups.com Subject: Re: [flexcoders] Could the Flex Gurus shed some light on this behavior? I believe since the content is a DisplayObject, it's just falling under normal Flex parenting rules

RE: [flexcoders] Could the Flex Gurus shed some light on this behavior?

From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of Mike Anderson Sent: Wednesday, April 23, 2008 1:07 PM To: flexcoders@yahoogroups.com Subject: [flexcoders] Could the Flex Gurus shed some light on this behavior? Hello All, For the longest time, I've been wondering why 2

[flexcoders] Could the Flex Gurus shed some light on this behavior?

Hello All, For the longest time, I've been wondering why 2 Loader Controls, are unable to share the same content. Then again this may be by design, and my lack of knowledge relating to Flex could be why I don't understand this. For example, I have a SWFLoader Control which comprises the

Re: [flexcoders] Could the Flex Gurus shed some light on this behavior?

I believe since the content is a DisplayObject, it's just falling under normal Flex parenting rules, a child can only have a single parent, so using the same content actually re-parents the content object to the new SWFLoader. If your navigation window is just a small preview of the total app,