Hi Ian > Gen - it shouldn't generate an error to have exactly the same class in > parent and child swfs.
Oops, my bad. I didn't test it with files in same domain. It did work if as long as its in same domain. > It's much more likely that you're either hitting an ApplicationDomain > issue of some sort (or a security error). The two SWFs should be in > the same application domain and security sandbox (however you achieve > that - I've no idea what your setup is). I never had even thought about the SecurityDomain class so I tried below. [code] var context:LoaderContext = new LoaderContext(false, ApplicationDomain.currentDomain, SecurityDomain.currentDomain); And this worked like a charm. Thanks! well...there is a side-effect. its just annoying while authoring since it throws errors. And here are the files used for testing. http://www.zenoplex.jp/test/event/event.zip > 2008/6/24 Gen <[EMAIL PROTECTED]>: > >> So I guessing, having same namespace/class name in parent and child >> swf will generate an error. I tried changing the ApplicationDomain >> but that didn't help either. > > Gen - it shouldn't generate an error to have exactly the same class in > parent and child swfs. > > It's much more likely that you're either hitting an ApplicationDomain > issue of some sort (or a security error). The two SWFs should be in > the same application domain and security sandbox (however you achieve > that - I've no idea what your setup is). > > Ian > _______________________________________________ > Flashcoders mailing list > [email protected] > http://chattyfig.figleaf.com/mailman/listinfo/flashcoders > > _______________________________________________ Flashcoders mailing list [email protected] http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
