Other things to investigate

Just some notes about where I'm looking, that seem interesting even though I have fuzzy ideas at best.

Skimming the hit test logic. This is relevant to custom display objects, but of course "manual touch" is probably handled somewhere in here.

On that note, looking a bit at masks, in particular as they relate to hit tests. (Was this the relevant proposal?) I think there's some opportunity in using a CPU-side buffer (could be 1-bit or 8-bit, or maybe a summed area table) to service "masked" tests, derived from the image data. This would of course fall down on stuff like regularly updated memory bitmap masks. (Heh, sounds like just bringing the topic up in Slack has moved Vlad's own idea along these lines forward.)

Also investigating fonts / text and where some sort of advanced text support might fit in. I sort of see where the logic lies, although obviously it has implications such as the aforementioned hit testing. Both myself and others have dabbled in some plugins, released or not, so maybe would have some useful ideas here... wondering if some kind of in-between system is possible, perhaps with whatever the "custom display objects" stuff becomes.

I wonder if an "I'm ready!" callback wouldn't be useful in some places, say with the splash plugin or asynchronous texture loads.

Plugins-wise, I need to eventually nail down some edge cases that luaproc needs to handle, painful as this sounds. ☹️ (Ideally, any actual work here would be on the plugin side.)

All of this is medium-priority at best, favoring low.