« Hide

Steps to reproduce:
1. Create multiple Modules in a project
2. Add them to the main.mxml with <mx:ModuleLoader />
3. Make sure the project uses RSLs for the Flex Framework instead of merging it into the code.
4. Run the project.
 
 Actual Results:
Not all Modules are being displayed. Sometimes only one and other times none at all.
The Modules are being loaded fine when we check the ModuleEvent.bytesloaded and ModuleEvent.bytesTotal. However the ModuleEvent.READY is not always being dispatched when loading is completed.
 
 Expected Results:
All modules should display. The ModuleEvent.READY should be dispatched when loading is completed.
 
 Workaround 1:
 When we first unload the Modules with Module.unloadModule() and then load them with module.loadModule() things are working fine, most of the times but not always. Workaround 2 might be the better solution.

 Workaround 2 (thanks to Gustavo Saume):
 Loading the modules as a sequence appears to solve the problem.

 Developers NOTE:
This only happens when we use RSL caching of the Flex Framework. Without the caching it all works fine. Looks like a part of the Flex Framework has not been completely loaded when the Modules are. See the attachment for a project replicating this issue.
 
 

Show »

Steps to reproduce: 1. Create multiple Modules in a project 2. Add them to the main.mxml with <mx:ModuleLoader /> 3. Make sure the project uses RSLs for the Flex Framework instead of merging it into the code. 4. Run the project.    Actual Results: Not all Modules are being displayed. Sometimes only one and other times none at all. The Modules are being loaded fine when we check the ModuleEvent.bytesloaded and ModuleEvent.bytesTotal. However the ModuleEvent.READY is not always being dispatched when loading is completed.    Expected Results: All modules should display. The ModuleEvent.READY should be dispatched when loading is completed.    Workaround 1:  When we first unload the Modules with Module.unloadModule() and then load them with module.loadModule() things are working fine, most of the times but not always. Workaround 2 might be the better solution.  Workaround 2 (thanks to Gustavo Saume):  Loading the modules as a sequence appears to solve the problem.  Developers NOTE: This only happens when we use RSL caching of the Flex Framework. Without the caching it all works fine. Looks like a part of the Flex Framework has not been completely loaded when the Modules are. See the attachment for a project replicating this issue.