When <> is not true block

gdfsgdfsgdfg

when <>  is not true :: events :: hat

Its not

when <> is true :: events :: hat

I bet it has a easy workaround

Last edited by gdfsgdfsgdfg (Nov. 18, 2022 15:49:16)

Knightbot63

when green flag clicked
forever
if <[whatever] = [true]> then
...
end
end

workaround

Last edited by Knightbot63 (Nov. 18, 2022 15:44:59)

randomguy3513

<not <>>

Easy workaround if when the “if <> is true” gets implemented

gdfsgdfsgdfg

some scratch blocks also have easy workarounds

for example:

next costume

workaround:

switch costume to (join [] [next costume])

Last edited by gdfsgdfsgdfg (Nov. 18, 2022 15:54:43)

randomguy3513

gdfsgdfsgdfg wrote:
next costume
workaround:
switch costume to [next costume v]

that doesn't work…

gdfsgdfsgdfg

#5

fixed it

gdfsgdfsgdfg

next backdrop

workaround:

switch backdrop to [next backdrop v]

randomguy3513

gdfsgdfsgdfg wrote:
next backdrop
workaround:
switch backdrop to [next backdrop v]

at this point your block spamming a little bit, please stop.

-Valtren-

still, not functions are really simple. there's no need to add it

gdfsgdfsgdfg

bump

NotDucki_

I'm not very certain in the use of this being a script starter. I can see it being used in the middle of a script for something.

I haven't used scratchblocks in years, apologies if this is a bit messy.

when I receive [event v]//This example is just assuming you are activating it with an event.
when [necessity v] is not true {
say [use a workaround!]} :: control

Now, you could use

<not <(foo) = (moo)>>//foo would be the value you are trying to determine is true or false, and moo is the value that foo has to match up to in order to be true.

For example:

if <not <(foo) = (moo)>> then
say [hello world!]
end

I would like to note that I have not touched Scratch in months, but I am fairly certain that the given workaround should work

cookieclickerer33

gdfsgdfsgdfg wrote:
when <>  is not true :: events :: hat
Its not
when <> is true :: events :: hat
I bet it has a easy workaround

Maybe this?

when <mouse down?> is [true v] ::events hat

And

when <mouse down?> is [false v] ::events hat

-Valtren-

why exactly is it so hard to use the workaround?
another one btw, this one works more like hat blocks.

when green flag clicked
forever
wait until <not <condition :: sensing>>
do something
wait until <condition :: sensing>
end

many blocks have simple workarounds, yet they're still here. but the thing is, they're needed, either because they help learn to code(the point of scratch) or because the simple workaround isn't so simple for someone just starting out.
While I would agree that

when <> is true :: hat :: events

is a good and needed block, a version of this for false booleans isn't in my opinion.

Last edited by -Valtren- (Nov. 29, 2022 15:10:18)

An0therRand0mC0der

Yes, you told us that some blocks have an easy workaround. However, why can't you just do this?
What's so hard about chucking 2 blocks together?
Please elaborate more and I will decide my full opinion on this suggestion.

if <not <...>> then
...
end

An0therRand0mC0der

Also this is a duplicate

-Valtren-

An0therRand0mC0der wrote:
Also this is a duplicate

it isn't. this one is for when the boolean is false. that one is for when the boolean is true

An0therRand0mC0der

-Valtren- wrote:
(#16)
An0therRand0mC0der wrote:
Also this is a duplicate
it isn't. this one is for when the boolean is false. that one is for when the boolean is true

Mentioned here

-ErrorPurpl_157

when I receive [… v]
forever
if <not <condition :: grey>> then
…
end
end

-Valtren-

An0therRand0mC0der wrote:
-Valtren- wrote:
(#16)
An0therRand0mC0der wrote:
Also this is a duplicate
it isn't. this one is for when the boolean is false. that one is for when the boolean is true
Mentioned here

but it's not specifically what the OP is suggesting.

cookieclickerer33

when [ timer v] > ((timer) - <not <custom condition ::custom>>)

Discuss Scratch