Actually yeah that might make sense

is there anything "magic" about substate?

or is it just for organisational purposes?

Nah there’s just some logic to update the main state or not

If it’s a pause menu or just an overlay

The ideal doesn't work, no.

However, the last one, the proposal, does work and does come being just one line off the ideal.

It uses the class I asked if we could look at rolling in.

Miss when I had a server in my apartment, was quite easy to push such things >.<

Typically people will make a backsplash to the substate.

Well, insofar as I've seen.

Also, bonus "because I slaughter everything" points here for my morning, the alphabetical order is the same as the written order. XD

MSGhero, I don't know whether I have an answer to: > And the haxe UI substate kinda defeats the purpose of HaxeUI, which is to blend seamlessly into your existing workflow I would have to see a worked example of it properly cooperating in the same FlxGroup as other objects, colliding, etc. The impression I'm under is that, as the label on the tin implies, it's reasonable for UIs, menus, that sort of thing. So to say it "blends seamlessly" seems to suggest it has some magical power to overcome that fundamental design aspect. It is a servicable, cross-library UI library/etc. Sure. It shows potential and I have hope. Sure. I'm willing to wrestle it to the ground and poke it hard, sure. :eyebrowwiggle: But being said, it's relegated to the space of UIs and menus in my workflow. Nothing more. This is especially ironic given that the current text adventure work I'm doing is all UI, and the entire playstate is basically HaxeUI with a background, using Flixel as the backend for no other reason than it's familiar XD

It's way too many sleep-deprived words for "I fail to see what's wrong with building out a pause menu with this, and the kit to do it trivially with. I'd - in fact - expect that to be a prime use."

shouldnt it "cooperating in the same FlxGroup as other objects, colliding, etc"? I mean, a Button is just a FlxGroup at the end of the day, no?

no. 😄

I'm not sure at the underlying level what a Button is.

But objects are arranged in groups.

at least not FlxButton, but that's probably not relevant here

So any object in that group should be able to collide.

it ends up as a FlxGroup i think

i mean a haxeui button

isnt any component in haxeui-flixel just a FlxGroup?

Again, I can't answer that. I can say that I would assume sooner or later we get down through some nesting of FlxGroups to objects that should be collidable with some certainty, at least.

Could probably ask for type and see what happens, lazy excuses here.

pretty sure it does... checking now

FlxSpriteGroup

not sure if thats different

Typed version of FlxGroup.