Discuss Scratch

AllenderaGames
Scratcher
100+ posts

Let's make 2 new blocks for true and false for sensing

undeterminstic wrote:

bump
what
-Rodri
Scratcher
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

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
Scratcher
100+ posts

Let's make 2 new blocks for true and false for sensing

-Rodri wrote:

this could only be used for quizzes, and the workaround isn't rocket science

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
Checking if a Sprite is touching an edge

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
Scratcher
1000+ posts

Let's make 2 new blocks for true and false for sensing

AllenderaGames wrote:

-Rodri wrote:

this could only be used for quizzes, and the workaround isn't rocket science

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
Checking if a Sprite is touching an edge

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
Checking if a Sprite is touching an edge

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
Scratcher
100+ posts

Let's make 2 new blocks for true and false for sensing

Question: Should it be a Boolean or a Reporter?
medians
Scratcher
1000+ posts

Let's make 2 new blocks for true and false for sensing

AllenderaGames wrote:

gdfsgdfsgdfg wrote:

thedogcoder440 wrote:

quite a few workarounds like

ask [2x2.5] and wait
if <(answer) = [5]> then
say [correct!] for (2) secs
end

so no support

EngineerRunner wrote:

half support, useful but with really easy workaround
workarounds anit a reason to not support
there is some blocks like:
next costume
which has an easy workaround
but it was added
someone that understands!
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 case

Powered by DjangoBB