cool - you shouldnt need that when i push this set of changes...

I have a (potentially dumb) question: I want to make a native application with access to the

sys

APIs - is there any backend that gives me particular advantages or disadvantages for that?

haxeui-flixel, haxeui-openfl : should work well, support both cpp and hl. haxeui-nme : cpp only, idk how well it works haxeui-hxwidgets : cpp only, and depends on wxwidgets haxeui-qt : wip, cpp only, and depends on qt haxeui-kha : cpp only, and you're stuck with khamake haxeui-heaps : hl only, has a few bugs

Awesome, thank you

Seems like the OpenFL backend is my best bet

Kha has both hl/c and cpp :3

It's hlc backend is buggy af, and Rob couldn't care less about it.

a fair point, i haven't used it in a while 😂

(And hlc still compiles quite slowly)

it was fully implemented by someone else iirc

I think it was lubos (the armory person)

thanks for answering Zeta 🙂 Been sick as hell last week+, feel like i might be coming out of it finally now, hope so anyway

I have another question, regarding using threads for longer running tasks Is it safe to directly set the state of components from other threads, or can this cause issues? If the latter, what is the best way to get data from a different thread? Super simplified example to illustrate (

btn

is just a regular

Button

and

lbl

a

Label

)

haxe
btn.onClick = (e) -> {
            btn.color = "red";
            btn.allowInteraction = false;
            lbl.text = "Running";
            sys.thread.Thread.create(() -> {
                Sys.sleep(1);
                lbl.text = "Idle";
                btn.color = "gray";
                btn.allowInteraction = true;
            });
        }

It would likely work more or less fine, but since components have a lot of properties, they could call functions that are not safe to call outside of the main thread. So I wouldn't really recommend using threads for that kind of stuff. (And if you just want to execute something after a specific delay, I would recommend using

haxe.Timer.delay

or a backend-specific equivalent)

The

Sys.sleep

is just to simulate the thread running for some time My current use-case would be to scan through a few thousand files, do some modifications and then report back to the user which files were affected. Doing this on the UI thread would obviously be bad, so I need to move the operation into its own thread.

What I would do : update loop on UI thread which checks wether the worker thread has done it's work, and handles updating the UI.

How can I hook into HaxeUIs update loop? I can't seem to find anything I could hook into

I don't think haxeui has a real update loop. The closest thing I can find is

haxe.ui.util.Timer

there's

haxe.MainLoop.add()

that might work

Heavily depends on the backend, openfl for example has a blocking update loop which stops the haxe loop from running. It's probably best to hook into backend specific update loops.

I wasn't able to find how HaxeUI hooks into the OpenFL update loop either, do you have some link/source code info about it?

I'd just use an enter frame listener.

isn't this what

haxe.ui.CallLater

is supposed to do

Call Later only executes once.

he only wanted it to run once, right?

Alright thanks - that seems like a good reference

So I'd have to write something to handle the ENTER_FRAME event and check for my thread being done - shouldn't be too much work

yeah this is exactly what

CallLater

does on

haxeui-openfl