Haxe

Ha ha, sometimes, we just need a break ^^

yeah, fresh eyes usually triumph... thats why dogs help... when i "rage quit" i take one of the dogs for a walk and by the time i look at it again im like "jfc - im a moron" 😄

Hi ! I downloaded this git <https://github.com/fredlangva/HaxeUI_Base> to have a sample of HaxeUI on Heaps. It helped me well for a few things but when I build then run it, all the texts are upside down. I thought it was a specific issue of this project so I didn't mind much. Although, when I managed to load fonts aswell on my project, I ended u having the same issue. The text from HaxeUI are upside down if I use another font than the default one (not the texts I manually display with the Heaps API and the same font). The git and I are using different fonts. Does anyone know what could go wrong there ?

what about in "normal heaps", ie, remove haxeui from the equation ... haxeui-heaps isnt doing anything special here afaik

It works if I do it myslef, with the same font, using Heaps h2d.Text

I downloaded the project yesterday and text was all fine

It seems it uses these 4 libs, do you have them all from git ?
-lib heaps
-lib hlsdl
-lib haxeui-core
-lib haxeui-heaps

Also, there is a *-D linux* going around, makes me wonder, what is your OS ? ^^

hldx: git [dev:C:\HaxeToolkit\haxe\lib\hldx\git\libs\directx]
hlsdl: git [dev:C:\HaxeToolkit\haxe\lib\hlsdl\git\libs\sdl]

do you have the above dev path as your selected option?

I had to change a few things, though, to make it work

the ``launch.json`` had originally :
```"configurations": [
    {
        "name": "HXCPP",
        "type": "hxcpp",
        "request": "launch",
        "program": "${workspaceFolder}/bin/yourExecutable.exe"
    }
]```

But I had to change it to (getting inspiration from another project of mine) :
```"configurations": [
    {
        "name": "HXCPP",
        "type": "hl",
        "request": "launch",
        "cwd": "${workspaceRoot}",
    }
]```

neither of these configs recompile the project when you run it

I mean, I downloaded all over again to spot/remember differences, I know have 2 different folders ^^

try running a build task then running hl gc.hl

I'm using VSCode, pressing F5 does recompile before running. Although I tried it manually (Ctrl+Shift+B) then ran and it was the same :(

pressing f5 in vscode doesn't auto recompile the project

Oh, it doesn't ? It does take it time, though, thought it was. My bad :D

you have to specify that in the launch. json which you just showed me that it doesn't <:eyey:809883715995959306>

there's a 'run build task' config that you can set on the launch task

just be mindful of that as you test things

Did you manage to get the project started without changing anything ?

Alright, I've tried it in command lines and still have the upside down issue

That's strange. Gonna try some haxelib update 🤷

Updated, reverted changes in the libs and still broken. Damnit, it's not gonna be fun to find :/

its a such a strange effect... so hang on though, you said that without haxeui its all fine, correct?

are you using any special params for the font?

i think you might need to register your sdf font width haxeui

```
                var sdfDetails = SDFFonts.get(_fontInfo.name);
                if (sdfDetails != null) {
                    font = _currentFontData.toSdfFont(defaultFontSize, sdfDetails.channel, sdfDetails.alphaCutoff, sdfDetails.smoothing).clone();
                } else {
                    font = _currentFontData.toFont().clone();
                    isBitmap = true;
                }
```

try putting: `SDFFonts.register("foo")` somewhere

For the Heaps way, I just do that :
```var font = new hxd.res.BitmapFont(hxd.Res.ui.themes.kenney.fonts.kenvector_future_thin_fnt.entry).toFont();
font.resizeTo(16);
var tf = new h2d.Text(font, root);
tf.text = "POUET !";
tf.textColor = 0xffffff;
tf.setPosition(200, 100);```
I don't change the font

The font is an FNT file (with an associated PNG file), it seems it's what Heaps likes 🤷

```ase: [2.0.1]
castle: 1.6.1 [git]
deepnightLibs: 1.0.70 1.0.72 1.0.74 [git]
differ: [1.4.0]
domkit: [git]
format-tiled: [2.1.0]
format: [3.5.0]
hashlink: 0.1.0 git [dev:C:\HaxeToolkit\haxe\lib\hashlink/git/other/haxelib/]
haxe-concurrent: 4.0.0 4.1.0 [5.0.3]
haxeui-core: 1.5.0 [git]
haxeui-heaps: 1.5.0 [git]
heaps-aseprite: [git]
heaps: 1.9.1 [git]
hldx: 1.10.0 1.13.0 git [dev:C:\HaxeToolkit\haxe\lib\hldx/git/libs/directx]
hlopenal: [1.5.0]
hlsdl: 1.10.0 git [dev:C:\HaxeToolkit\haxe\lib\hlsdl/git/libs/sdl]
hscript: 2.4.0 [git]
hx3compat: [git]
hxbit: [1.5.0] git
hxnodejs: [git]
ldtk-haxe-api: [git]
partials: [1.0.0]
redistHelper: 0.6.0 0.7.0 [0.7.3]
seedyrng: [1.1.0]
stb_ogg_sound: [0.0.2]```

I've tried 2 path (I never know which one to use with Heaps resource system ^^') and it either didn't change or I got that :

It's the kenvector_future_thin gone through a software to generate  FNT+PNG files ^^

Alright ! I used the same font as HaxeUI_Base in my own project and it works !

So, it must be registered (it's strange NotBilly doesn't need to do it, though) and the software I've user must have done smth wrong for the kenney font

So, since im wanting to release a new version of haxeui, and i cant be bothered to do it all manually, ive decided to breathe some life into my haxelib manager again, this time using <@539190724030103553> 's haxelib lib which makes it _much_ easier to work with haxelib... progress so far is pretty nice 🙂

these kinds of qol apps are exactly what I want to use haxeui for <:blobcheer:964199767217410158>

yeah, really nice having that lib and just not thinking (so much) about the haxelib integration, my previous version was this kinda bastardization of haxelib via sys.process and "recreating" haxelib client (ie, reading files and whatnot - basically what you have done, but you've done it properly)

Yh, haxelib was really needing a clean up 😅

still some work left to do though, I've been putting off some improvements to haxelib git bc the update/installation code for git libraries is still not perfectly clean

cool - well, its a great effort, for sure - means you _can_ write 3rd party tools (like this one) with relative ease...

mainly just cloning without the entire history, something i've been talking about for ages... 😅

but the code is still a bit messy which made it a pain to change so i ended up putting it off and haven't gotten back to it