How can I set the property ? I need the reference of the object and object is created while I am getting the reference ?
May be I am missing something, I will check. Thanks, Serkan Android için Outlook'u edinin On Mon, Nov 25, 2019 at 8:14 AM +0300, "Alex Harui" <[email protected]> wrote: Royale will not guarantee the timing of Flex. Flex didn’t really guarantee the timing of creationComplete either. If your component forced a validateNow() the creationComplete would happen in the same place. It is probably best to rewrite that to instantiate and call addPopUp after setting properties. My 2 cents, -Alex From: Serkan Taş <[email protected]> Reply-To: "[email protected]" <[email protected]> Date: Sunday, November 24, 2019 at 9:21 AM To: "[email protected]" <[email protected]> Subject: Function call sequence Hi, In my application I have menu item and a handler which opens file view popup. It is highly dependent on the function calls of component creation. While debugging the code; private function showGenericPopup(fileTag:String):void { var fileViewWindow:FileViewPopup = PopUpManager.createPopUp(parentApplication as mx.core.IUIComponent, FileViewPopup, true) as FileViewPopup; fileViewWindow.isNativeXML = true; fileViewWindow.fileTag = fileTag; //"joblog=" + jobDetailLocalXml.@Id; PopUpManager.centerPopUp(fileViewWindow); fileViewWindow.setFocus(); } the function defined above is called, · in Flex, the "creationComplete" related function of FileViewPopup is called at the line "PopUpManager.centerPopUp(fileViewWindow);" · in Royale, the "creationComplete" related function of FileViewPopup is called at the line "var fileViewWindow:FileViewPopup = PopUpManager.createPopUp(parentApplication as mx.core.IUIComponent, FileViewPopup, true) as FileViewPopup;" So in royale some attributes are not yet set while the component is created. What should be the right behavior ? Is this a bug or new implementation is decided like above ? How should I overcome this issue ? Thanks, Serkan
