revisit: it occurs to me that i missed your point - killing off the event before it fires, not killing off the object at end of event. oh well, i should just be quiet now, as the “let corona do everything automatically” approach is essentially the opposite of how i work: if i create an object that registers an event, it is also responsible for removing it, and is stored in my own lists (and don’t rely on display groups for “ownership” OR disposal), etc. and instead of adding “helper” routines to try to patch all the edge-cases where doing stuff automatically fails, i have a helper that can verify that a group is EMPTY prior to removal (otherwise that’s a sign i’ve forgotten to code something somewhere). i also reference count my create/destroy’s, and tag objects with unique keys (can print during debug if something is found to be “lingering” to help track them down). sounds like a lot of work? it’s really not - what sounds like a lot of work to me is constantly trying to hunt the bizarre “doesn’t work automatically” stuff like this. my personal motto: do it all explicitly and know it was done (and when), rather than implictly and hope. i’m not saying my way is “better” or trying to recruit you to my camp, but just as reason why my tool kit doesn’t have the right kind of duct tape in it for this.
