Workers - I thought there was a topic for this already

General
1

So we now have workers that are threaded so they’ll spawn off, do what they need to do and then callback to the stack that called them.

You can dispatch to the worker from anywhere in the stack, but callback messages are handled in the stack script only.

2 Likes
2

that’s reasonable, even expected.
mmmmmmm drones…i mean threads…although technically minions…
now…before the multithreaded minion ossifies, and in anticipation of building for mobile and the web, can we have both multithread and singlethreaded behavior?

3

Sorry, it’s one or the other and 0.9.11 had the single-threaded mode, which really didn’t offer any benefits - it was pretty much the same thing as a send/dispatch, it still ran on the main thread and could block the UI. This threaded approach allows you to run large tasks on a different thread and get notified when it is done.

1 Like
4

ok. when and if we get to deploy on singlethreaded architectures, some other solution will have to suffice - as it has since forever.

5

and last question: is sharing still out? is there any passing references/values, or just messages?

6

You can pass text/numbers/encoded image data/etc but you cannot pass control references, ByRef variables, etc

7

so passing, but no sharing