Hi Doug, I was just trying to understand what the Flex code looked like to make sure you were using the right Royale code. IIRC, in Flex there was a ModuleLoader that loaded a Module and created a single instance of its main class, expecting it to be UI. I didn't think you could pass parameters to it when loading. There was also a ModuleManager that loaded modules that extended ModuleBase. That one I think you could pass parameters. I don't think we've created a Royale equivalent for ModuleManager/ModuleBase scenarios.
Note also that Royale modules do not unload at this time. Probably for a while. Have you run the examples/royale/ModuleExample? It sets up the bin/js-debug output in a particular folder structure and I think a bit differently for bin/js-release. Maybe that example will contain the clue you need. HTH, -Alex On 4/2/18, 10:58 PM, "doug777" <[email protected]> wrote: >Hi Alex, > >Main.mxml contains initialView/View and a bunch of getters and setters. > >Inside this View is a header group, a body group that contains the modules >and a footer group. Originally the modules were contained in a ViewStack, >but I've written something I hope will replace this, but I can't check it >until the modules can build. > >The first module gets data from CF and then depending on the choices the >user makes, the second module gets appropriate data from CF and is >displayed >in place of module 1 and so on depending on the choices made in each >module. >The modules can appear in any order depending on user choice. > >I'm not sure what that has to do with getting the modules in the build, >but >basically that's how it works. > >Doug > > > >-- >Sent from: >https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-roy >ale-users.20374.n8.nabble.com%2F&data=02%7C01%7Caharui%40adobe.com%7C3064f >c565fc948905b5a08d59927fa2f%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C6 >36583319358141648&sdata=OyQo%2BFRiiCRFkN3fHfGpqnhnO1C%2FjVEuu9%2FmOUiYMZs% >3D&reserved=0
