1 person found this helpful
Your assumptions about ApplicationDomain.currentDomain is incorrect. When you request ApplicationDomain.currentDomain you get what is effectively a constant, but in the context of the SWF containing the code making the call.
Flex SDK Developer
Adobe Systems Inc.
Thanks for the to-the-point answer, Alex!
A follow-up on this: Is it correct to assume then if I load A.swf and B.swf into the same application domain, and C.swf into a child applicationDomain of A.swf, then C.swf should inherit class definitions from both A.swf and B.swf (and D.swf concequently from all of the others)?
And what about loading using loadForCompatibility? Does that place the loaded swf into a sibling application domain compared to the swf that did the loading, or compared to the root swf (i.e. a child of the system application domain)? E.g. in my example, if C.swf loads D.swf using loadForCompatibility, is D.swf placed in a sibling application domain compared to C.swf or A.swf?
Thanks, Alex. Based on this, I think I have the application domain logic figured out in my head now also.