Hi Hiedra, Brian, I did most of the work on Crux porting, and it's entirely possible there are bugs in the port. Feel free to open a github issue. It will be easier for me to work on it if there is a minimal repro fileset that you can attach to the issue. If something relied on weak listeners in the original Swiz, it could be part of the reason, but I would need to try to compare and debug swiz vs. crux to check. I'd be happy to look into it but I am unlikely to be able to get to it until July 3 or 4 because of other commitments.
Greg On Thu, 24 Jun 2021, 7:09 pm Maria Jose Esteve, <mjest...@iest.com> wrote: > Hi Brian, it happens to me too and I have not managed to solve it. In my > case, I include the mxml instantiation is maintained, maybe because it does > the crux.... link. > > Hiedra. > > -----Mensaje original----- > De: Brian Raymes <brian.ray...@teotech.com> > Enviado el: miércoles, 23 de junio de 2021 21:37 > Para: dev@royale.apache.org > Asunto: Crux Not Cleaning Up EventHandlers Upon Tear Down? > > Hi all, > > I have a puzzling situation. I am dynamically adding crux views that > contain reusable components that contain EventHandler tags. When I remove > said component and add another, the previous instance of the Crux > EventHandler is not removed. Instead, another is added. > > Destroying that view by tearing down the bean does not seem to remove the > EventHandler that was previously associated. Instead, the new view adds > another, then subsequent dispatched events now invoke the EventHandler > twice. Destroy and add another, then three times, etc. > > Is this expected? Is there away to force the EventHandler to cleanup? > Should I be using the Prototype class to instantiate single instances? If > so, can someone point me towards how that can be done on the fly? > > > Thank you. > > Brian > >
