Haxe

<@361318220147458059>  - so just to understand the issue is that the tab key isnt working correctly?

also, you mentioned haxeui-kha doesnt work with new-component branch? Can you elaborate? Seems to work for me

seems to work for openfl (tabbing)... though i would also expect the scrollview to scroll with the tabbing, which im going to fix now

have i just go the total wrong end of the stick here?

Can you customize the keys and also go backwards?

Or potentially customize the direction it goes? I made a custom thing using the arrow keys to jump around to non-grid aligned buttons

yeah, it needs some work for sure (the general FocusManager) but a basic impl is there

the idea, eventually, is to be able to handle totally custom ways to "get around"... like tabbing, arrows, gamepad, etc

but focus manager hasnt been touched it a fair amount of time, so certainly needs some love

your arrow key work would almost certainly be good to look at... you got it online anywhere?

Nah and it was very hacky, like  diving into HaxeUI private vars

But essentially, each button was represented by a node with a `to` array of nodes and `back` node

yeah, focus manager would need some type of "hints" to allow for things like arrow key / gamepad / tv remote navigation

To was like keyboard key => next node, back was a single key for moving back a menu kind of thing

which is fine for desktop, but not so much for other input methods

but it has the ability to push and pop views, so _should_ be able to be fairly clever about things - but again, needs some real love... this issue above is the first time ive looked at it in i dont know how long... maybe from the initial inception? :/

ScrollView::ensureVisible was a worthwhile method to add anyway, even if the focus manager gets totally rewritten

Could not get FlxSubstate working for the life of me nicely with HaxeUI.

The UI didn't seem to listen to parent pause.

And the toolkit seemed fixated on the main state's ui flxgroup instead of the substate's (within scope of the substate itself)

It's on my list to create a proper test case project, but just be aware "this is a thing that happened"

<@283780995453419522> when you init the toolkit, what does that look like?

If you specify the state or don’t specify anything, it uses the FlxState

IIRC, the substate isn’t a child of the state so it never gets seen by HaxeUI