When <> is not true block

medians

Why “not true” when that can be false??

meepmep_

This is a problem that the

if <> then 

  

else

end

block takes care of

Last edited by meepmep_ (Nov. 30, 2022 16:57:18)

owlover2010

I like the idea, but events blocks are already slow. I would use this workaround:

when green flag clicked
forever
if <> then
...
end
end

I do not give support for this suggestion.

cs3868895

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

Ok, I need that instead to be a block, N o w first

Last edited by cs3868895 (Dec. 2, 2022 06:14:47)

cookieclickerer33

cs3868895 wrote:
gdfsgdfsgdfg wrote:
when <>  is not true :: events :: hat
Its not
when <> is true :: events :: hat
I bet it has a easy workaround
Ok, I need that instead to be a block, N o w first

when [ timer v] > ((timer) - <not <not<When value here>>>

gdfsgdfsgdfg

bump

An0therRand0mC0der

Are there any benefits to adding this block? Considering the workaround for this is already easy and functions the same.

hill_walker123

cookieclickerer33 wrote:
cs3868895 wrote:
gdfsgdfsgdfg wrote:
when <>  is not true :: events :: hat
Its not
when <> is true :: events :: hat
I bet it has a easy workaround
Ok, I need that instead to be a block, N o w first
when [ timer v] > ((timer) - <not <not<When value here>>>

when [timer v] > ((timer) - <...>) // when <> is true
when [timer v] > ((timer) - <not<...>>) // when <> is false

Last edited by hill_walker123 (Dec. 2, 2022 15:50:11)

gdfsgdfsgdfg

the purpose
of this block

when <> is true ::events :: hat // is that it can't be stopped so it can do some workarounds like this
when <key [ v] pressed?> is true ::events :: hat

// =

when [ v] key pressed

An0therRand0mC0der wrote:
Are there any benefits to adding this block? Considering the workaround for this is already easy and functions the same.

Last edited by gdfsgdfsgdfg (Dec. 2, 2022 15:55:15)

hill_walker123

gdfsgdfsgdfg wrote:

the purpose
of this block

when <> is true ::events :: hat // is that it can't be stopped so it can do some workarounds like this
when <key [ v] pressed?> is true ::events :: hat

// =

when [ v] key pressed

then just use

when [ v] key pressed

however if it's the other thing you might be saying, then:

when [timer v] > ((timer) - <...>)
repeat until <not <...>>
...
end

Last edited by hill_walker123 (Dec. 2, 2022 15:56:45)

gdfsgdfsgdfg

hill_walker123 wrote:

gdfsgdfsgdfg wrote:

the purpose
of this block

when <> is true ::events :: hat // is that it can't be stopped so it can do some workarounds like this
when <key [ v] pressed?> is true ::events :: hat

// =

when [ v] key pressed

then just use

when [ v] key pressed

bruh Im talking about how you can do some workarounds for this block

Last edited by gdfsgdfsgdfg (Dec. 2, 2022 15:56:31)

hill_walker123

gdfsgdfsgdfg wrote:
hill_walker123 wrote:
gdfsgdfsgdfg wrote:
the purpose
of this block
when <> is true ::events :: hat // is that it can't be stopped so it can do some workarounds like this
when <key [ v] pressed?> is true ::events :: hat

// =

when [ v] key pressed
then just use
when [ v] key pressed
bruh Im talking about how you can do some workarounds for this block

…

gdfsgdfsgdfg

Bump

GUYWHOLOVESCODE

A lot of people ignored the fact that you're asking for an Events block. My suggestion for the workaround:

when green flag clicked
wait until <not < > >

and then the code meant to happen here. Do you want it to wait until a broadcast is sent to start checking?

when I receive [ v]
wait until <not <>>

That's really all I got for you.

Xcvfdd

No support. The workaround is easy:

<not <key [ v] pressed?>>

Or

forever
if <not <key [ v] pressed?>> then

end
end

BrodyTheRedflower

No support, do this easy workaround

when green flag clicked
forever
if <[thing] = <not <thing>>> then
...

end
end

_ProjectDev

when green flag clicked
forever
if <not <[x] = [y]>> then
...
end

_ProjectDev

GUYWHOLOVESCODE wrote:
A lot of people ignored the fact that you're asking for an Events block. My suggestion for the workaround:
when green flag clicked
wait until <not < > >
and then the code meant to happen here. Do you want it to wait until a broadcast is sent to start checking?
when I receive [ v]
wait until <not <>>
That's really all I got for you.

If you want it to continue waiting after it's not equal or continue doing the thing while it's equal you can put it in a forever loop

cookieclickerer33

randomguy3513 wrote:
<not <>>
Easy workaround if when the “if <> is true” gets implemented

There’s an easy workaround for if <> is true as well

-Valtren-

cookieclickerer33 wrote:
randomguy3513 wrote:
<not <>>
Easy workaround if when the “if <> is true” gets implemented
There’s an easy workaround for if <> is true as well

which is precisely why it's not added yet.

Discuss Scratch