Alrighty, rest well.

thanks Shaun, you too 🙂

This all looked to work! However, I potentially worked myself into an accidental corner. Curious your thoughts on this: I'm building a little app in HaxeFlixel (that may be obvious already from my previous questions). I was actually building it to be an android app. I just migrated all of my UI over to haxe-ui, testing on desktop as I go. Now that I'm "done", I went to test it on Android to see if it works properly and it doesn't look like the flixel backend is set to work on mobile. Any suggestions? Or am a little SOL here?

hmmm, yeah - its a good point... the issue, as far as i remember, is that haxeui-flixel doesnt scale (at all)...

i think it should though as its certainly a valid usecase (and every other backend scales correctly and so there can be used on mobiles)...

if you give me a few days ill sort it out - its been on "the list" for an age, but ill bump it up to high priority since i think it defo should work with scaling

to confirm, thats the issue right? The UI is tiny?

UI run on windows

UI run on Android

The top window is what I want it to look like (it's not done, but the proportions are all nice and a good chunk of functionality is sorted out. I did have to make one change to get it to compile, namely, in

haxe/ui/backend/flixel/MouseHelper.hx

I hacked it to not be dependent on mouse (which isn't available on mobile devices) to look like:

haxe
    private static function get_buttonPressed():Int {
        var n = -1;
        #if mobile
        if (FlxG.touches.list.length > 0) {
            n = 0;
        }
        #else
        if (FlxG.mouse.pressed == true) {
            n = 0;
        } else if (FlxG.mouse.pressedRight == true) {
            n = 1;
        }
        #end
        return n;
    }

Which I'm sure isn't the ideal solution, but it got me building, at least. Then I saw the UI was a little wonky.

Also for clarity, the white/gray grid and the little gray rectangle with

!"#$....

in it are both flixel things. The rest are haxeui elements.

OK, so yeah, maybe its not "too small" but it all looks related to sizing type issues... should be fairly easy to sort out

I can try tomorrow when I get some time to see if some of the elements are getting lost behind my flixel stuff (namely behind the white/gray grid). I would agree that it feels like it's a sizing thing, but hard for me to be certain of that. It's way too far past my bedtime for me to do more digging tonight. If I spot anything else curious/useful tomorrow, I'll post some updates here.

sure - im basically 99.9% sure its all related to haxeui-flixel NOT scaling correctly...

if you bear with me for a few days, ill sort it - needs to be done anyway as its the only composite backend that doesnt scale (i think)

almost have my website layout completed using haxeui, just need to get the animated title and the quotes moved over. And figure out why autoplay wants to drive me nuts instead of autoplaying. 🙂

seems to be working nicely... and all pretty simple as expected (thats a screen from my actual device) - just want to test a few more components before i commit

🥳

Well that seemed shockingly quick... Especially for being done in the middle of the night (for my timezone, at least) 😂

🙂

be interested to see how it works with your app - but in my tests it seems fine now on mobile

looks like it's already committed to the repo. I'll give it all a try this evening and see how it looks. Theoretically, I'm not doing anything complicated. I'm just using some buttons and then some Box elements to act as guides for where to put some Flixel elements (basically just using their coordinates to guide where I place / size some cameras and such)

screenshot from my device. It's clearly much, much better now. Looks like the way I was grabbing coordinates to align my elements isn't quite working -- but won't be able to dig into that until this evening at best.

What's funny is that the 3 elements I'm basing off of the haxeui elelments look like they are positioned correctly relative to each other - so I'm guessing it's that the scaling factor isn't reflected in the top/left and the width/height properties of the elements.

you might have to use "actualWidth" and "actualHeight" now

or, alternatively multiply by Toolkit.scale

What a about for the proper way to get x/y (left/top seem more reliable), then? Same thing? Just go with the Toolkit.scale for that, too? As a side note, it seems like the positional coordinates don't get set as expected when I first init the Toolkit and load my menu. I basically wait for one update call, then align everything. It's no big deal for me to code around, but I just wanted to throw that out there in case it's something silly. But anyway, I'll try using the Toolkit scale to get my other stuff lined up / scaled properly later today. Thanks!

i think left / top will also be in "non scaled" co-ords, so yeah, you'll need to * by scale... maybe an "actualLeft" and "actualTop" would be useful properties

> As a side note, it seems like the positional coordinates don't get set as expected when I first init the Toolkit and load my menu. I basically wait for one update call, then align everything. Hmmm, ill check it out