Discuss Scratch

Jonathan50
Scratcher
1000+ posts

Asynchronous Custom Blocks

Bump.
liam48D
Scratcher
1000+ posts

Asynchronous Custom Blocks

Support!
Jonathan50
Scratcher
1000+ posts

Asynchronous Custom Blocks

Bumpidy bumpidy bump!
ChildCritic
Scratcher
500+ posts

Asynchronous Custom Blocks

octad wrote:

75% as per above.

Blank1234 wrote:

workaroundable by using broadcast blocks
no support
Blank, just because it's workaroundable does not necessarily justify or warrant a no support.
He, Like I do, doesn't mind fairly tedious workarounds.
Anyways, Semi-support since there is a workaround.
MegaApuTurkUltra
Scratcher
1000+ posts

Asynchronous Custom Blocks

Support
Jonathan50
Scratcher
1000+ posts

Asynchronous Custom Blocks

Bump
Jonathan50
Scratcher
1000+ posts

Asynchronous Custom Blocks

BIIIIG Bump
Leadrien2366
Scratcher
100+ posts

Asynchronous Custom Blocks

Support.
Arthurtilly
Scratcher
1000+ posts

Asynchronous Custom Blocks

No support, easy workaround.
...
broadcast [continue v]
...

when I receive [continue v]
...
Jonathan50
Scratcher
1000+ posts

Asynchronous Custom Blocks

Arthurtilly wrote:

No support, easy workaround.
...
broadcast [continue v]
...

when I receive [continue v]
...
?
Arthurtilly
Scratcher
1000+ posts

Asynchronous Custom Blocks

What do you mean? It's a simple workaround for your idea.
Jonathan50
Scratcher
1000+ posts

Asynchronous Custom Blocks

Arthurtilly wrote:

What do you mean? It's a simple workaround for your idea.
I don't understand it… do you mean like using callbacks?
Arthurtilly
Scratcher
1000+ posts

Asynchronous Custom Blocks

I mean, that if you call a broadcast in the middle of a script then you can run it like a custom block on a seperate thread. If you want parameters:
...
set [continue? v] to [false]
set [variable v] to (whatever :: grey)
broadcast [continue v]
wait until <(continue?) = [true]>
...

when I receive [continue v]
block (variable)

define block (parameter)
set [continue? v] to [true]
forever
...
end
Jonathan50
Scratcher
1000+ posts

Asynchronous Custom Blocks

Arthurtilly wrote:

I mean, that if you call a broadcast in the middle of a script then you can run it like a custom block on a seperate thread. If you want parameters:
...
set [continue? v] to [false]
set [variable v] to (whatever :: grey)
broadcast [continue v]
wait until <(continue?) = [true]>
...

when I receive [continue v]
block (variable)

define block (parameter)
set [continue? v] to [true]
forever
...
end
Ok, I have that in the OP, but it can get a little tedious if you have a threading-centric project.
Arthurtilly
Scratcher
1000+ posts

Asynchronous Custom Blocks

But that's only if you need parameters, and if the parameter changes right away. For no parameter, you can use broadcasts.
Jonathan50
Scratcher
1000+ posts

Asynchronous Custom Blocks

Bump
comp09
Scratcher
1000+ posts

Asynchronous Custom Blocks

I support this - I don't want, for example, the custom block that renders the display with pen to interfere with other scripts in the project.
Scratcher1002
Scratcher
1000+ posts

Asynchronous Custom Blocks

octad wrote:

75% as per above.

Blank1234 wrote:

workaroundable by using broadcast blocks
no support
Blank, just because it's workaroundable does not necessarily justify or warrant a no support.
Truth, PLUS the workaround is nearly IMPOSSIBLE to incorporate into a 1s1s project.
Support.
Dylan5797
Scratcher
1000+ posts

Asynchronous Custom Blocks

Support. I really need this, broadcasts are too slow to rely on in my case.
Scratcher1002
Scratcher
1000+ posts

Asynchronous Custom Blocks

bump

Powered by DjangoBB