There is no issue with initComplete or almost all the issues reported today excet one ! I learned by now that when there is a new bug on the Royale framework then everything can be broken like domino and I need to find the source of the first issue. I will post the only one real issue in a separated github/email.
Hugo Ferreira <[email protected]> escreveu no dia sexta, 4/09/2020 à(s) 11:25: > OK, I will insulate my issue because there is now code involved until I > find out what is going on and then I back here. > > > Carlos Rovira <[email protected]> escreveu no dia sexta, 4/09/2020 > à(s) 11:04: > >> Hi Hugo, >> >> just tried this and is working: >> >> j:Application xmlns:fx="http://ns.adobe.com/mxml/2009"; >> xmlns:j="library://ns.apache.org/royale/jewel" >> xmlns:js="library://ns.apache.org/royale/basic" >> initialize="initApp(event)"> >> >> <fx:Script> >> <![CDATA[ >> import org.apache.royale.jewel.Card; >> import org.apache.royale.events.Event; >> >> private var card:Card; >> >> public function initApp(event:Event):void >> { >> card = new Card(); >> card.addEventListener("initComplete", initCompleteHandler); >> view.addElement(card); >> >> } >> >> private function initCompleteHandler(event:Event):void >> { >> trace("hey!!") >> } >> ]]> >> </fx:Script> >> >> >> >> >> El vie., 4 sept. 2020 a las 10:31, Hugo Ferreira (<[email protected] >> >) >> escribió: >> >> > I have a Jewel Card that is created and added at runtime after a login. >> > I have code on initComplete of this Card. >> > The event don't fire any more (without console errors) after I upgrade >> to >> > last night build. >> > >> >> >> -- >> Carlos Rovira >> http://about.me/carlosrovira >> >
