title is self explanatory.

@greenFlag green flag clicked? :: sensing boolean

//or

@greenFlag green flag clicked? :: events boolean

You couldn't activate this block without the green flag being clicked in the first place.

No support, the boolean wouldn't even check if the green flag wasn't clicked, so this block is useless.

Edit: Ninja'd

zHmonster wrote:

You couldn't activate this block without the green flag being clicked in the first place.

?

first of all, the

when green flag clicked

is good enough, why would we need sensing blocks for it? Scripts can't run without you pressing the Green Flag in the first place.

hehe everyone is forgetting that you could use one of the other hats that could be true before you hit the green flag; especially "when [space v] key pressed". You might want to prevent a script under one of the other hat blocks from running before you've even started the project.

But there's a really easy workaround:

when gf clicked 
set [flagged? v] to [1] 
when [space v] key pressed 
if <(flagged?) = [1]> then 
... :: looks  
end 

So no support anyways.

Why would this be beneficial to scratch?




no support

IndianRuby718 wrote:

hehe everyone is forgetting that you could use one of the other hats that could be true before you hit the green flag; especially "when [space v] key pressed". You might want to prevent a script under one of the other hat blocks from running before you've even started the project.

But there's a really easy workaround:

when gf clicked 
set [flagged? v] to [1] 
when [space v] key pressed 
if <(flagged?) = [1]> then 
... :: looks  
end 

So no support anyways.

No support because:

when green flag clicked
set [flagged v] to [1]

and the above workaround.

IndianRuby718 wrote:

hehe everyone is forgetting that you could use one of the other hats that could be true before you hit the green flag; especially "when [space v] key pressed". You might want to prevent a script under one of the other hat blocks from running before you've even started the project.

But there's a really easy workaround:

when gf clicked 
set [flagged? v] to [1] 
when [space v] key pressed 
if <(flagged?) = [1]> then 
... :: looks  
end 

So no support anyways.

oh ok I did not think of that (scratch team please close this topis)

sathvikrias wrote:

zHmonster wrote:

You couldn't activate this block without the green flag being clicked in the first place.

?

The green flag must have been clicked for this boolean to function, as nothing (except trickery with the timer) can run without the green flag being clicked.

sathvikrias wrote:

IndianRuby718 wrote:

hehe everyone is forgetting that you could use one of the other hats that could be true before you hit the green flag; especially "when [space v] key pressed". You might want to prevent a script under one of the other hat blocks from running before you've even started the project.

But there's a really easy workaround:

when gf clicked 
set [flagged? v] to [1] 
when [space v] key pressed 
if <(flagged?) = [1]> then 
... :: looks  
end 

So no support anyways.

oh ok I did not think of that (scratch team please close this topis)

There should be a button that lets you close the topic. If not, I can report this to be closed.

IndianRuby718 wrote:

when gf clicked 
set [flagged? v] to [1] 
when [space v] key pressed 
if <(flagged?) = [1]> then 
... :: looks  
end 

And one more thing, make sure the variable is at 0 when opening the project. To make sure it's at 0 when stopping the project you can use the workaround for “when stop sign clicked”. That one's in the sticky for workarounds.