Make sure you have a reference to the moduleInfo otherwise a GC can kick it out. Post the code that starts the load.
________________________________ From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of Marvin Froeder Sent: Monday, February 11, 2008 10:15 AM To: flexcoders@yahoogroups.com Subject: [flexcoders] ModuleManger I was looking into the ModuleManager code, and found something wear. /** * @private */ public function completeHandler(event:Event):void { //trace("child load of " + _url + " is complete"); var moduleEvent:ModuleEvent = new ModuleEvent( ModuleEvent.PROGRESS, event.bubbles, event.cancelable); moduleEvent.bytesLoaded = loader.contentLoaderInfo.bytesLoaded; moduleEvent.bytesTotal = loader.contentLoaderInfo.bytesTotal; dispatchEvent(moduleEvent); } I begin look after that when my modules stop loading (after update from flex 2 to flex 3) and no error event was dispatched. So, any suggestion? My module don't dispatch ModuleEvent.READY or ModuleEvent.ERROR. Only ModuleEvent.PROGRESS events. This may be the problem source? I try to mimic my complete handler when moduleEvent.bytesLoaded == moduleEvent.bytesTotal but no success... Any know workaround? All my modules use RSL. Is that a problem? VELO
