I think you'd have to debug through it and see what is going on. However, before doing that, is it possible to re-implement this set of apps? Do these sub-apps ever need to run on their own? If not, you should consider using Modules. If that's too big an effort but those sub-apps don't need to run on their own, you should not build them using RSLs and simply extern all of the classes in the RSL when you build them. It will prevent them from even trying to load the RSL, but they'll remain small and run fine because they'll find the classes in the main app's applicationDomain. This should make your sub-apps show up even faster since they don't need to wait for the 3MB RSL load. I would expect this to solve your problem as well as there might be issues when more than one loader is trying to load the same bits.
________________________________ From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of Nick Durnell Sent: Wednesday, December 19, 2007 2:53 AM To: flexcoders@yahoogroups.com Subject: [flexcoders] Re: Problem with RSL and SWFLoaders --- In flexcoders@yahoogroups.com <mailto:flexcoders%40yahoogroups.com> , "Alex Harui" <[EMAIL PROTECTED]> wrote: > > I would try to find out what happened to the other 9? Are they showing > progress bars? Is the app stuck? Is CPU usage running high? Hi Alex, I do not see any progress bars for the applications which fail to start. CPU usage is at 0% once the application has 'stuck'. I've also tried with fewer widgets and get the same problem. As long as there are more than one being loaded at once (which share an RSL), one of them fails to start. Is there anything I can do to check what Flash is doing behind the scenes? Any other events on the SWFLoaders/Applications it may be useful to listen for? Regards, Nick.
