Xcvfdd wrote:

No support. The workaround is easy:

<not <key [ v] pressed?>>

Or

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

end
end

_ProjectDev wrote:

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

BrodyTheRedflower wrote:

No support, do this easy workaround

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

end
end

These workarounds will stop if the stop sign is clicked or the stop block


When is true is a block that cant be stopped

when [timer v] > ((timer) - <…>)

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.

owlover2010 wrote:

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.

same for these

gdfsgdfsgdfg wrote:

These workarounds will stop if the stop sign is clicked or the stop block

How can something become true or false while the project is stopped? The project needs to be running for a certain condition to be met.

gdfsgdfsgdfg wrote:

These workarounds will stop if the stop sign is clicked or the stop block

isn't that the point? the stop sign is supposed to stop all scripts.

An0therRand0mC0der wrote:

gdfsgdfsgdfg wrote:

These workarounds will stop if the stop sign is clicked or the stop block

How can something become true or false while the project is stopped? The project needs to be running for a certain condition to be met.

Not true at all. You can have projects function that doesn't use the green flag entirely using the other hat blocks. The hat blocks always check if their condition is met after the project is started; after that, the stop button doesn't do anything. This normally is not a problem since they're all really basic things like whether the timer is greater than a certain value or a key is pressed, but allowing any boolean value to be checked if this block were added would lead to major issues. For example, if a variable is greater than five, you could run some code that crucially does not change that variable's value to be less than five, creating code that can never be stopped.

bump