Discuss Scratch

1800_m1necr4ft
Scratcher
21 posts

new block suggestions

hi. i was thinking that we could post ideas for new blocks such as commands and booleans. one of my ideas is this:
<[message1 v] has been received?>
it checks to see if a message has been received.
for example:
when I receive [start v]
repeat until <[start v] has been received?>
turn cw (45) degrees
wait (0.5) secs
turn ccw (90) degrees
wait (0.5) secs
end

show list [ things that describe me]

// |
//\|/

1: Ten-year-old Minecraft lover
2: technology enthusiast
3: trying to figure out how to get garageband on the raspberry pi that i am using right now
xXRedTheCoderXx
Scratcher
1000+ posts

new block suggestions

Sorry mate, but that suggestion was rejected by the Scratch Team
1.1 “Broadcast received” boolean block
The block below would allow a project to detect when a broadcast is sent. But, there is a lot of ambiguity on how this would work. Would it return true if the broadcast was fired since the project was created, since the green flag was clicked, or since something else was broadcasted? The workaround is simple: use variables that change when a broadcast is received, then use the “equals” block.

However, the blocks “repeat until broadcast received” and “wait until broadcast received” are NOT rejected; you can discuss them on this post.

<[message v] received? :: events>

1800_m1necr4ft
Scratcher
21 posts

new block suggestions

looks like everything i suggest is rejected by the scratch team.
anyway, another suggestion is the
(if <> then () else ())
reporter. if the boolean is true, then the reporter output is the first input. if the boolean is not true, then the output is the second input.
this
set [random variable v] to (if <mouse down?> then (1) else (2))
instead of the workaround:
if <mouse down?> then 
set [random variable v] to [1]
else
set [random variable v] to [2]
end

show list [ things that describe me]

// |
//\|/

1: Ten-year-old Minecraft lover
2: technology enthusiast
3: trying to figure out how to get garageband on the raspberry pi that i am using right now
xXRedTheCoderXx
Scratcher
1000+ posts

new block suggestions

1800_m1necr4ft wrote:

looks like everything i suggest is rejected by the scratch team.
anyway, another suggestion is the
(if <> then () else ())
reporter. if the boolean is true, then the reporter output is the first input. if the boolean is not true, then the output is the second input.
this
set [random variable v] to (if <mouse down?> then (1) else (2))
instead of the workaround:
if <mouse down?> then 
set [random variable v] to [1]
else
set [random variable v] to [2]
end
Please post new suggestions in a different topic. Also, before you post any suggestion, make sure to read the entire rejected suggestions sticky.

Powered by DjangoBB