If you’re writing a custom component, you might want to override addedToParent() to achieve what you need. With PAYG there are less baked-in lifecycle events and hooks, but there should be nothing stopping you from adding these events where you actually need them.
As Piotr said it would be helpful to understand a more specific scenario here. From: Piotr Zarzycki<mailto:piotrzarzyck...@gmail.com> Sent: Thursday, July 9, 2020 8:37 AM To: Apache Royale Development<mailto:dev@royale.apache.org> Subject: Re: creationComplete event Hi Hugo, Well in the end you are in a different world after compiling application. initComplete is notifying you once element is added to DOM, so this is real equivalent to what we had in Flex. What's the issue in your sight? Thanks, Piotr On Thu, Jul 9, 2020, 1:40 AM Hugo Ferreira <hferreira...@gmail.com> wrote: > I know that Royale is not intended to be backward compatibility with Flex. > I know that but my question is not the case. > I think that a creationComplete or if you prefer a ready event or > childrenComplete is important. > The initComplete is good to start initializing things as soon as possible > however to work with components a creationComplete is very important to > iterate with components. > There is also a childrenAdded however seems to run after initComplete and > before a possible creationComplete so it's a irrelevante event. >
