Haxe

<@!525025580106907659> the lime changes broke my Android build :(
```
Error: Source path "C:/HaxeToolkit/haxe/lib/lime/git/ndll/Android/liblime-v7.so" does not exist
```

Since you switched to lime git, you'll have to rebuild the lime native libraries.
`lime rebuild android -with some flags i'm not sure about`

After updating lime to git develop... FileDialog is giving this output for a selected file
```
"㩃啜敳獲䝜極敦屳潗歲灳捡履慈數灜楲敭物桡硡履獡敳獴瑜硥畴敲慰正牥捜慨慲瑣牥⹳獪湯"
```
😄

btw, which translates to: "This is the best way to get the most important thing for the year-round."

<@!385014891750096896> Rob Conrad has proven to not be very helpful in resolving an bug with his code as it relates to loading assets from a non-standard location using a file path. So as far as adding the sounds specific to a theme, I don't believe that may be resolved, requiring the sounds to be placed in the "Assets" directory.

<@!385014891750096896> Seems like haxe ui flixel backend doesn't work properly when added to a FlxSubState

Wrong positions and wrong click collisions as well 😦

<@!281900608678658049> What's this bug you speak of? I would like to see it and see if I can see if there was a misunderstanding somewhere.

I probably missed it - but do you have an example anywhere of what that, the code, looks like? Sorry!

I'll try to isolate the problem in a small separate project and post here

Aigh, sorry, I thought had narrowed it down to FlxSubState, but it's not it.

I'm still trying to figure out what the problem is, but I just managed to reproduce it without a substate

If you get it to a simple enough point, it will be awesome if you can confirm it's Flixel specific or not

<@!223621181138272256> - lemme know if you are still having issues / able to reduce to a simple eg... everything seems all good this end

<@!126172290667773952> - the target for that "multi focus" was windows.. but i think i saw it on html5 too

I finally managed to recreate and reproduce it.

It seems that is has more to do with the moment you either instantiate ou stage it. If I do it later on, say in a callback of some UI things get weird.

Ignore the name. Has nothing to do with substate.

Just click the "New Game" button in the UI. That should add another component to the screen that won't work correctly at all. <@!385014891750096896> <@!99004666821500928>

<@!223621181138272256> - should be working now

np - another oversight on my part wrt to haxeui-flixel 🙂

good to find all these little annoyances 😉

The irony is killing me, but it still behaves the same when instead of staging it directly, you stage it in an FlxSubState

I'll change the example project to the new situation

At least now the name of the project makes sense 😄