not implemented on wxWidgets thought unfortunately for me...

@User on thread safety - you need to use synchronisation primitives (lock and mutex) if you’re changing properties on objects shared between threads otherwise you’ll be likely to get memory corruption

I agree it’s better to use the event loop for this sort of async work as single thread perf very often not be a bottleneck Threads are great but unfortunately haxe doesn’t provide built -in safety so they can be a foot-gun

Where would I put a lock in my own code to prevent the UI thread from accessing the (component) properties I'm mutating?

Typing on mobile so apologies for the pseudo code, but you could create a mutex alongside the btn variable, then any time you read or write to this variable you need to do mutex.acquire(); btn.color = “blue”; mutex.release(); Thank will mean only one thread will be changing properties at a time

This doesn't help at all, the UI framework itself has no idea it's supposed to acquire a mutex before it reads the

btn.color

property

agreed, I think threads are not the right fit here, what’s the use case? For scheduling calls to run in the future haxe.Timer.delay the right way to go

I already explained my use-case: I'm running some heavy filesystem operations (involving multiple threads and tons of files)

The suggestion from Zeta to create a class that keeps checking whether the operations are done is exactly what I need to solve this

I'll most likely also include the haxe-concurrent library, since it has a nice looking

Executor

and

Future

implementation, which simplifies this checking further

In general, a better solution here would be to spawn a standalone thread (assuming you actually do some work on the files, otherwise just normal event loop should suffice), and it will report back with data, in some event-driven approach. Only the main thread would ever touch the UI stuff. Not unlike how it would work in JS.

How would I set up such an event-driven approach in HaxeUI then? I haven't found anything built-in that would allow me to do it Also last I worked with JS it was still single-threaded, asynchronous operations were implemented in coroutine style (and therefore no synchronization primitives were required)

No clue about haxe-ui really, but in general it would have to be some message queue system. Not sure Haxe has that implemented, though I think it does have event loop in nightlies now.

In JS you can spawn a worker, it runs on a separate thread, but doesn't share any memory.

if ur using openfl you can use a

Deque<Void->Void>

that is emptied in an EnterFrame openfl event which runs all the tasks that were queued.

What it can do is send/receive messages, which are triggered as callbacks, so it can work in standard asynchronous coroutine style.

that's what im doin with my async socket at least

If there's nothing in Haxe for this, you could simply have some sort of

msg

array that you fill in from the thread, and check on the main thread, and of course lock the access via mutex to it.

How is that different from Zeta's suggestion? It sounds like the exact same thing to me

There's

Thread.readMessage

and

thread.sendMessage

sys.thread.Deque

is built in

I suppose it's not. Sorry, missed that bit when skimming in the morning.

So (very) late to the party, but yeah, basically, what everyone said here is how i would advise... I created / used a task manager for my HaxelibManager that does ALOT in the background, reading local file system, making http calls, libGit2 calls... alot

This is the basic manager... its still a wip, and it actually needs a little redesign - not because it doesnt work - but because it could be a little simpler, but the general idea is there which might help as a ref

( @User )

Thanks, that's a good reference 👍

I'd like to try to make a haxeui program that gives the user an interface to select a list of elements having an associated sound and then plays the element's sounds sequentially and at intervals. I believe I'll just need haxeui and maybe a timer to achieve this, but feel free to correct me if I'm wrong. I was wondering about how to setup and start this project, since I'd like to support more targets in the future (android, linux, macos...) but I'd just be interested in html5 and windows for now. Any insight is appreciated

> I believe I'll just need haxeui and maybe a timer to achieve this, I think that would make sense, i guess it depends how well you need the sounds timed... if you are thinking of like a sequencer then i think you'll need something cleverer, but if you are just saying "play this sound every second" then i think timer would be up for the job

for this project I believe I would just need to play a sound every 1-2 seconds and it doesn't have to be perfectly timed, however there is another project I'd like to do next (and for which I'd like to try and reuse some code) that will basically be the same program as this but instead of playing a sound it should show an image for split seconds, there I would need to see the difference between showing the image for 0.1 secs or 0.4

basically a tachistoscope