Discuss Scratch
- Discussion Forums
- » Suggestions
- » Let's make 2 new blocks for true and false for sensing
- AllenderaGames
-
100+ posts
Let's make 2 new blocks for true and false for sensing
what bump
- -Rodri
-
1000+ posts
Let's make 2 new blocks for true and false for sensing
this could only be used for quizzes, and the workaround isn't rocket science
wait.. what would u even use “activate true/false” for?????? I think i just wrote what u had in the op just without the blocks, and it'd still work
set [true] to [21]
if <(answer) = (true)> then
broadcast [true]
when I receive [true]
say [correct!] for (2) secs
change [score] by (1)
end
wait.. what would u even use “activate true/false” for?????? I think i just wrote what u had in the op just without the blocks, and it'd still work
- AllenderaGames
-
100+ posts
Let's make 2 new blocks for true and false for sensing
Checking if a Sprite is touching an edge this could only be used for quizzes, and the workaround isn't rocket scienceset [true] to [21]
if <(answer) = (true)> then
broadcast [true]
when I receive [true]
say [correct!] for (2) secs
change [score] by (1)
end
wait.. what would u even use “activate true/false” for?????? I think i just wrote what u had in the op just without the blocks, and it'd still work
when green flag clicked
forever
if <<touching [edge v] ?> = (true::sensing)> then
say [Sprite is touching edge] for (2) secs
end
end
Message when Mouse clicks an sprite
when this sprite clicked
forever
if <<mouse down?> = (true::sensing)> then
say [Sprite was Clicked] for (2) secs
end
end
- undeterminstic
-
1000+ posts
Let's make 2 new blocks for true and false for sensing
Checking if a Sprite is touching an edgeChecking if a Sprite is touching an edge this could only be used for quizzes, and the workaround isn't rocket scienceset [true] to [21]
if <(answer) = (true)> then
broadcast [true]
when I receive [true]
say [correct!] for (2) secs
change [score] by (1)
end
wait.. what would u even use “activate true/false” for?????? I think i just wrote what u had in the op just without the blocks, and it'd still workwhen green flag clicked
forever
if <<touching [edge v] ?> = (true::sensing)> then
say [Sprite is touching edge] for (2) secs
end
end
Message when Mouse clicks an spritewhen this sprite clicked
forever
if <<mouse down?> = (true::sensing)> then
say [Sprite was Clicked] for (2) secs
end
end
when green flag clicked
forever
if <touching [edge v] ?> then
say [Sprite is touching edge] for (2) secs
end
end
Message when Mouse clicks an sprite
when this sprite clicked
forever
if <mouse down?> then
say [Sprite was Clicked] for (2) secs
end
end
- AllenderaGames
-
100+ posts
Let's make 2 new blocks for true and false for sensing
Question: Should it be a Boolean or a Reporter?
- medians
-
1000+ posts
Let's make 2 new blocks for true and false for sensing
The name is confusing then, since people might believe that it's a block that reports true/false. Also, if it means something that checks if the answer inputted is true, it might be difficult to know if was the correct answer or if it is true when it's something like “What was (insert here)'s dog's name?” It would probably not be able to know in this casesomeone that understands!quite a few workarounds likeask [2x2.5] and wait
if <(answer) = [5]> then
say [correct!] for (2) secs
end
so no supportworkarounds anit a reason to not support half support, useful but with really easy workaround
there is some blocks like:next costumewhich has an easy workaround
but it was added
- Discussion Forums
- » Suggestions
-
» Let's make 2 new blocks for true and false for sensing