a google search for moduleFactory.info shows that Adobe uses that approach in mx.effects.EffectManager which you can see here: http://bit.ly/nKums.
Type: Posts; User: tombray; Keyword(s):
a google search for moduleFactory.info shows that Adobe uses that approach in mx.effects.EffectManager which you can see here: http://bit.ly/nKums.
I was able to get the module's applicationdomain by using this.moduleFactory.info().currentDomain. See the code below to test it out:
<?xml version="1.0" encoding="utf-8"?>
<mx:Module...