Hi Mark, going by parts:
El lun., 25 mar. 2019 a las 18:07, Kessler CTR Mark J (<[email protected]>) escribió: > Using Royal SDK 0.9.4 binaries with a Jewel Card / Basic Group my recommendation is not use such older version. Many many changes was done after 0.9.4. I think you should use a nightly build as a minimum (and if you plan to do Royale development seriously, my recommendation is you work with the latest develop branch, since we are improving and fixing in a day-by-day basic. Is strange the day we don't push new changes ;) > and ran into an issue where the "this" reference is not ready / comparable > while in an "initComplete" event handler. However after its full creation > cycle it is available and can be compared. I tested with a button calling > the same method as the initComplete did. Would have tried using a > "creationComplete" handler, but the event doesn't seem to exist. > > creationComplete does not exists. I think Alex could give more info about why is not. I must say that I *never* need that handler anymore, you can do almost all with "initComplete". I think "this" is always available within a component, so don't understand why a "initComplete" should not be valid for you. I just needed in more complex scenarios to use "beadsAdded" handler, for things in the life cycle of a component. > Searched the email archive and found the thread "Where is the > creationComplete in jewel ?", that states the init and completed events > were combined. What is the new preferred way to get a creationComplete > styled event or when it's 100% setup if the initComplete does not work or > is that a bug? > if initComplete is not working for you I think that's a bug depending on the scenario. Please describe the problem, the component that is dispatching the initComplete and a simple handler so we can give more details, if possible with a nightly build, since if not we can see different things than you see. > > > -Mark K > -- Carlos Rovira http://about.me/carlosrovira
