ok, thats "fixed" now (haxui-kha 1.0.1) thanks to @cuddly-hairdresser-69398, the fonts look pretty crappy though as they scale up 4x (on my device) but after they have already been drawn... so they dither 😦

i wonder if there is something clever i can do about that

maybe draw the fonts afterwards? Not sure

Shouldn't we redraw on scale ? @bright-gpu-74537 Idont know how fonts work though but do fonts have like differents sizes backed in them ?

In th ttf file I mean.

yeah, the ttf can show different size fonts... and smoothly, the issue is how haxeui-kha is scaling things... ... so, if you have Toolkit.scale=4 (for example) then haxeui draws the UI (and the text)... that is essentially just an image, it then scales that 4x... but from the original image

so the fonts look crappy

probably the best idea is that the calls that draw the UI in the first place should be aware of the scale to start with

so instead of, say,

line(x, y, w, h)

, it should be something like,

line(x*scale, y*scale*,w*scale,h*scale)

... etc

dunno how well that will work, but in theory it should be fine... will have to test it out

@bright-gpu-74537 Ah! Does this scaling thing relate to the event problems?

it did yeah

so your app works, but as you'll notice the text isnt crisp... will have to have a think about the best way to go about fixing it

i think probably to draw the UI with scale (as above) rather than upscaling a UI drawn at 1x

this is specific to haxeui-kha btw, other ones seem to autoscale fine

first time in a long time ive tested on kha android

@bright-gpu-74537 I dont know if you saw the pr's I did in september for haxeui-kha ? Do you want us to ping you in discord when we have something (because last time when I had fix/feature it went faster through here 🙂 ) I dont mind that a pr take time to be included but maybe you just dont know they exist so thats why I am bumping you here. https://github.com/haxeui/haxeui-kha/pull/36 Its maybe a time constraint and I would understand if so.

sweet, yeah, ill merge... honestly, its a little of "all of the above"... i must have known about this, as i would have got a notification

but seemingly totally forgot... so certainly doesnt hurt to ping me here and remind me, as its very possible that ive totally forgotten to merge it!

(merged... thanks!)

there is this one also: https://github.com/haxeui/haxeui-kha/pull/34

but it is open to discussion if it should be merged

hmmmpf... this i do remember looking at... i wonder if it was while things were still "new-component-method"

(also merged)

Its better for users to avoid Krom not working but at the same time this is hacky and should be fixed in kha

lol ok ;

sure, but as you said in the description, this is a decent enough work around until then

( I just dont have the knowledge to fix it in kha)

cool - well, i can see the linked issue and the krom issue, so all is well i think

ok good ! good day(or night) and thanks for the fast response