After googling more, I did find that this is marked as a defect with Adobe (sdk-24343 and sdk-14669). Although Adobe stated they fixed this issue in a 3.4 sdk version, there is enough replies to tell me they did not get it fixed.
One work around stated they had success manually dispatching the READY event from the progress handler when bytesLoaded == bytesTotal. I had zero luck with that, as I suspected. But, another work around so far is successful for me. I’ll know more after the rest of my team uses it for a few days since this is a “doesn’t always happen” bug. Instead of loading all my modules at one time, I load them sequentially. Yes, that is not as nice and goes a little against the purpose of modules, but so far is working and READY gets dispatch each time. I’ll certainly report back if it ends up not working. Dale From: [email protected] [mailto:[email protected]] On Behalf Of Scott Talsma Sent: Thursday, February 04, 2010 2:26 PM To: [email protected] Subject: Re: [AFFUG Discuss] Why isn't ModuleEvent.READY getting dispatched? This may be a major diversion for you, but I have seen significant issues related to whether the file being loaded was already in browser cache or not. When it is cache, not all the proper events fire all the time. And it only seems to be an issue w/FP10. I've only fought it was Loaders and SWFLoaders--not Modules, but the result sounded familiar, so I thought I would throw my experiences out there. HTH, Scott On Wed, Feb 3, 2010 at 9:00 PM, Dale Bronk <[email protected]> wrote: My application has 3 main modules. We download a small swf with a login page and while the login page is displayed and the user is logging in, we are downloading our 3 modules in the background. If the user clicks login before all are loaded, we see that and we wait for the modules to get loaded before we move forward with authentication. The problem we are having is that the ModuleEvent.READY event is not always being dispatched and I have no idea why. I've tried both ModuleLoader and ModuleManager. I could bring up the app several times in a row and everything is good. But then I'll pull it up again and see that maybe one of the modules did not dispatch READY. I have progress meters on them so I see they are all 100% downloaded. It is very strange because I can do this several times with no issues, then all of a sudden no more READY dispatched. If I clear my browser cache then all works again. We are using RSL for our framework. Here is the code I have for one of my modules. Others work the same. In the ready handlers we will use the factory.create, but it does not get there if the READY is not dispatched. Any suggestions? I have a feeling that it has something to do with the fact we are using RSL for our framework. When we were not using RSL, I did not have this issue. private var rtiModuleInfoProxy : IModuleInfo;rtiModuleInfoProxy = ModuleManager.getModule("rti.swf"); rtiModuleInfoProxy.addEventListener(ModuleEvent.READY, onRTIModuleReady, false, 0, true); rtiModuleInfoProxy.addEventListener(ModuleEvent.ERROR, onRTIModuleError, false, 0, true); rtiModuleInfoProxy.addEventListener(ModuleEvent.PROGRESS, onRTIModuleProgress, false, 0, true); rtiModuleInfoProxy.load(); Thanks, Dale ------------------------------------------------------------- To unsubscribe from this list, simply email the list with unsubscribe in the subject line For more info, see http://www.affug.com Archive @ http://www.mail-archive.com/discussion%40affug.com/ List hosted by http://www.fusionlink.com ------------------------------------------------------------- -- Scott Talsma CTO, echoEleven ------------------------------------------------------------- To unsubscribe from this list, simply email the list with unsubscribe in the subject line For more info, see http://www.affug.com Archive @ http://www.mail-archive.com/discussion%40affug.com/ List hosted by http://www.fusionlink.com -------------------------------------------------------------
