Haxe

And I’m rewriting the core HaxeUI flixel object, so I can do whatever I need to there

It's a really, really weird feature, in my defense.

So, somehow, I would make a callback to register if a state’s UI children need to be updated

I might also add a “stateInactive” callback to flixel itself, something along those lines

Are HaxeUI objects aware they belong to HaxeUI in a way that Flixel could see?

I’ll toss around some code and see what happens

So then the only viable attack point is the Toolkit's render group.

Or so it seems, just running my head over it with what I know and would try.

Well. Good luck. Let me know if you need me to retry my test cases.

Oh, kind of a hack, but what about “thisObjectWasUpdatedByFlixelLastFrame” as a sign to go ahead and process mouse events

Like you said, there’s really no access into that persistentDraw conditional, and no existing tie between the state’s update and mouse manager’s

The overhead needs to be noted for people using it.

A boolean? I wouldn't expect it to be too high.

And  hopefully either flixel's rearchitecture means we can just compose the object to not suck or else someone comes along with a brilliant solution later.

It would just be a Boolean or two I imagine

Wait, I’m not sure how I would be able to set it to false

I don’t want to put something like that in the render loop, but maybe I’ll have to...

IIRC flags are dealt with on `super.update()` for flxobjects, so

```haxe
public function override update(elapsed:whoCares)
{
    checkFlagAndDoStuff();
    resetFlag();
    super.update(elapsed);
}
```

went looking in docs, cannot find, do check

You can put that before parent's update function call from super.