Hi Doug, Can you give me a better idea of what the Flex code was? I'm wondering if the Flex code hooked an event like creationComplete that was sent top-down (parent then its children). In Royale, initComplete is sent bottom-up (children then parent). There is no top-down event in Royale at this time. We could create a bead that generates one, but I don't know if we want to bake it into the framework until we get more data. TBH, I never really thought about until now, but creationComplete in Flex is called way after creation is complete for deeply nested children since it is top-down.
Code order will probably not change between browsers. We are not creating threads at this time. So, don't move your code. If you need a top-down event, generate one and hook to it. Like a CreationCompleteBead. It might hook to applicationComplete and walk the containers top-down and dispatch "creationComplete" If you create a bead that does it, it would be great if you would submit to the project. We would use it in the emulation components. Thanks, -Alex On 4/29/18, 11:51 PM, "doug777" <[email protected]> wrote: Hi Alex, The as class is a kind of pop-up Alert. In the early parts of the actionscript code the first thing that happens is a RemoteObject gets called and the as class pops up a "Getting data" message. This happens in Main.init() and View2.init(). For some reason the first bit of actionScript to get built is View2.init() which then builds AlertPopup.as and then fails because Main.init() has not yet been built. (View1.init may also have run but the first Alert in here is in a second function called by View1.init) When running the code, the Alert in View2.init does not occur until after the user makes some selections in View1. I'm wondering if the order code is built would differ between browsers and processor speeds on different computers so that the order code is built is more or less random. Perhaps an answer would be to move all the code from Main and have it appear in a View0 whose init would then hopefully be built before View2. It looks as though applicationComplete is not called in JS until all the Views have been completely built whereas in Flex initComplete was called after the display objects were built. Doug -- Sent from: https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-royale-users.20374.n8.nabble.com%2F&data=02%7C01%7Caharui%40adobe.com%7Cc2d0e55cb37948cae7a408d5ae66c208%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636606678724389269&sdata=KxfoE849sPjZ3ZaPUYc9zGl2o8R7HxRnrvv%2F%2FfCJiJ0%3D&reserved=0
