DarthVader4Life wrote:

I think it should be called “broadcast and send.”

broadcast [message v] and send (var) :: events

broadcast (message v) with data (data)(data) ➖ ➕ ::events

broadcast (message v) with data (data)(data) ➖ ➕ ::events

d016 wrote:

DarthVader4Life wrote:

I think it should be called “broadcast and send” to keep with Scratch's desire to be easily understood.

broadcast [message v] and send (var) :: events

Nice idea, although I feel like “broadcast” and “send” are synonyms, so then this happens:

broadcast [data v] and send [message name] :: events

I'd use “with data:” instead:

broadcast [message v] with data: [cool idea! support] :: events

FreshTheCat wrote:

DarthVader4Life wrote:

I think it should be called “broadcast and send.”

broadcast [message v] and send (var) :: events

Yeah, this wording is better. But I'd like to change it *evil maniac laughter*

broadcast (message v) with data (data)(data) ➖ ➕ ::events

broadcast (message v) with data (data)(data) ➖ ➕ ::events

the minus-plus part was inspired by makecode, please tell me the minus and plus actually show up

DarthVader4Life wrote:

-snip-
Also, you did add in the multi-argument aspect of this suggestion, so not a complete ninja.
“with data” is probably the best simple wording to use, aside from maybe using “input(s).”

d016 wrote:

DarthVader4Life wrote:

-snip-
Also, you did add in the multi-argument aspect of this suggestion, so not a complete ninja.
“with data” is probably the best simple wording to use, aside from maybe using “input(s).”

I feel like “inputs” might be too confusing for some scratchers. It doesn't really matter if we can send multiple data pieces; even just one CSV value would be enough for 99% of all the problems this suggestion solves

Kanyata wrote:

-snip-
What is a CSV value again?

sandetsun wrote:

This is a great idea, and like newraf said it would definitely remove some unneeded temporary variables
Feels like a global custom block

when I receive [ v] (Argument1::events)@delInput@addInput <Boolean1::events>@delInput@addInput::events hat
broadcast ( v) []@delInput@addInput <>@delInput@addInput::events
broadcast ( v) []@delInput@addInput <>@delInput@addInput and wait ::events

CodeComet6161 wrote:

when I receive [ v] (Argument1::events)@delInput@addInput <Boolean1::events>@delInput@addInput::events hat
broadcast ( v) []@delInput@addInput <>@delInput@addInput::events
broadcast ( v) []@delInput@addInput <>@delInput@addInput and wait ::events

Kanyata wrote:

CodeComet6161 wrote:

when I receive [ v] (Argument1::events)@delInput@addInput <Boolean1::events>@delInput@addInput::events hat
broadcast ( v) []@delInput@addInput <>@delInput@addInput::events
broadcast ( v) []@delInput@addInput <>@delInput@addInput and wait ::events

This is an interesting take, almost like custom blocks

broadcast [message with inputs v] with [] []:: events

broadcast [message with inputs v] with [cake] (peppermint bark) :: events

when I receive [message with inputs v] with (input 1 :: events) (input 2 :: events) :: events hat

broadcast [message without inputs v]

when I receive [message without inputs v]