mybearworld wrote:

xXRedTheCoderXx wrote:

~sniper~

{define block 1
forever
. . .
end

define block 2
forever
, , , :: grey
end

event :: events hat
broadcast [Execute Block v]

when I receive [Execute Block v]
block 1

when I receive [Execute Block v]
block 2} ⠀⠀⠀⠀= ⠀⠀⠀{event :: events hat
do {
. . .
} while doing {
, , , :: grey
} :: control} :: reporter #aaa

Phew, making that took time

To much work. Support.

gosoccerboy5 wrote:

This is essentially the

launch {
script::motion
}::control

block from Snap!. It launches a script that runs while you run other scripts.
(Technically, it looks like

launch ({script::motion}::grey ring)::control

but Scratch isn't ready for grey rings)
So, no support. I'm going for a launch block.

lapisi wrote:

gosoccerboy5 wrote:

This is essentially the

launch {
script::motion
}::control

block from Snap!. It launches a script that runs while you run other scripts.
(Technically, it looks like

launch ({script::motion}::grey ring)::control

but Scratch isn't ready for grey rings)
So, no support. I'm going for a launch block.

just because a block is in Snap doesn't mean it shouldn't be in Scratch.

NanoPIex wrote:

PkmnQ wrote:

NanoPIex wrote:

-snip-
I`m not talking about custom blocks.

I think you no like read. I will explain in few words. Normal hat block work with two scripts, but custom block no work with that. Do you get now?

Ok, that might've been kinda insulting. I'll use normal sentences.

Normal hat blocks work with two scripts, but custom blocks don't.

I`m not talking about custom blocks!

fdreerf wrote:

That title is very long. All you really need to say is that there isn't a workaround.


-snip-

Tunde123 wrote:

fdreerf wrote:

That title is very long. All you really need to say is that there isn't a workaround.


-snip-

Read the title again. He is saying that people should read the entire OP. But people didn't seem to care to read it.

portalpower wrote:

also since they it's not possible to make this do you mean like alternating?
ex:

Do {
add [1] to [list v]
add [2] to [list v]
add [3] to [list v]
add [4] to [list v]
add [5] to [list v]
} while doing {
add [5] to [list v]
add [4] to [list v]
add [3] to [list v]
add [2] to [list v]
add [1] to [list v]
} :: control

the list would be 1,5,2,4,3,3,4,2,5,1

ResExsention wrote:

It's a cool suggestion, but I would not touch coroutines at all in a beginner programming language.

You on page 2 wrote:

Coroutines!

Support. Useful beyond belief.

fdreerf wrote:

I don't like the name of the block. I like the idea of being able to run two scripts at once* in an E block, but “do while doing” is such a clunky and inelegant name, especially with the verb “do”. I personally can't think of a better name, but it just feels gross to say and read.

fdreerf wrote:

That title is very long. All you really need to say is that there isn't a workaround.

xXRedTheCoderXx wrote:

fdreerf wrote:

I don't like the name of the block. I like the idea of being able to run two scripts at once* in an E block, but “do while doing” is such a clunky and inelegant name, especially with the verb “do”. I personally can't think of a better name, but it just feels gross to say and read.

Can't disagree there. The name used to be, “Run, while running,” as in, it runs code while running other code, but it was changed due to people thinking some people might be confused as new coders might not understand what run in this context means.

I honestly think I should get the old name back, what do you think?

run {
} and {
} ::control

broadcast [broadcast v]
when I receive [broadcast v]
block (1) ::custom
when I receive [broadcast v]
block (2) ::custom
define block (input)
if <(input) = [1]> then 

script 1... :: pen 

else
script 2... :: pen
end

sterngames wrote:

workaround is:

broadcast [broadcast v]
when I receive [broadcast v]
block (1) ::custom
when I receive [broadcast v]
block (2) ::custom
define block (input)
if <(input) = [1]> then 

script 1... :: pen 

else
script 2... :: pen
end

mybearworld wrote:

xXRedTheCoderXx wrote:

~sniper~

{define block 1
forever
. . .
end

define block 2
forever
, , , :: grey
end

event :: events hat
broadcast [Execute Block v]

when I receive [Execute Block v]
block 1

when I receive [Execute Block v]
block 2} ⠀⠀⠀⠀= ⠀⠀⠀{event :: events hat
do {
. . .
} while doing {
, , , :: grey
} :: control} :: reporter #aaa

Phew, making that took time

To much work. Support.

fdreerf wrote:

I think less is more when it comes to blocks. Perhaps

run {
} and {
} ::control

could work, though it'd be weird to refer to this block's name.

run {
} and {
run {
} and {
run {
} and {
run {
} and {
run {
} and {
} ::control} ::control} ::control} ::control} ::control

xXRedTheCoderXx wrote:

fdreerf wrote:

-snip-

Yes it could, and we could refer to it as a “Run, and run” E block.

run {
} and {
run {
} and {
. . .
} :: control} :: control

As that's what the blocks say when snapped together.

run ... and run ... and run ...

do ... while doing do ... while doing do ...

NanoPIex wrote:

PkmnQ wrote:

NanoPIex wrote:

-snip-
I`m not talking about custom blocks.

I think you no like read. I will explain in few words. Normal hat block work with two scripts, but custom block no work with that. Do you get now?

Ok, that might've been kinda insulting. I'll use normal sentences.

Normal hat blocks work with two scripts, but custom blocks don't.

I`m not talking about custom blocks!

PkmnQ wrote:

NanoPIex wrote:

PkmnQ wrote:

NanoPIex wrote:

-snip-
I`m not talking about custom blocks.

I think you no like read. I will explain in few words. Normal hat block work with two scripts, but custom block no work with that. Do you get now?

Ok, that might've been kinda insulting. I'll use normal sentences.

Normal hat blocks work with two scripts, but custom blocks don't.

I`m not talking about custom blocks!

I know, you were talking about the workaround. I was also talking about the workaround, which DOES NOT WORK WITH CUSTOM BLOCKKS PLEASE LEARN HOW TO READ

PkmnQ wrote:

PLEASE LEARN HOW TO READ

PkmnQ wrote:

I think you no like read. I will explain in few words. Normal hat block work with two scripts, but custom block no work with that. Do you get now?

lapisi wrote:

-snip-
NanoPlex wasn't talking about custom blocks so not working with custom blocks isn't actually important