k0d3rrr wrote:

graham3078 wrote:

Could you add a workaround for “when stop sign clicked”

Such as?
-
There are two methods (with reset timer and without reset timer).

Method 1 (thanks to the Scratch Wiki)

when green flag clicked
forever
reset timer
end

when [timer v] > (0.1)
...

Method 2

when green flag clicked
forever
set [timer v] to (timer)
end

when [timer v] > (timer:: variables)
...

when green flag clicked
forever
reset timer
end
when [timer v] > (0.1)
do something :: #080808

when [timer v] > (0.1)
forever
reset timer

graham3078 wrote:

Could you add a workaround for “when stop sign clicked”

when green flag clicked
forever
set [Stop v] to ((Timer)+[1]) :: variables
end


when [Timer v] > (Stop)
…

<this sprite holding?:: sensing

when this sprite clicked
set [l v] to [1]
wait until <not <mouse down?>
set [l v] to (0)
<(l) = (1)>// sprite holding?

Little_Mittle12345 wrote:

workaround for

<this sprite clicked?:: sensing

when this sprite clicked
set [l v] to [1]
wait until <mouse down?>
set [l v] to (0)
<(l) = (1)>// sprite clicked?

Little_Mittle12345 wrote:

workaround for

<this sprite clicked?:: sensing

when this sprite clicked
set [l v] to [1]
wait (0) secs
set [l v] to (0)
<(l) = (1)>// sprite clicked?

(backdrop count ::looks)

define backdrop count
set [save v] to (backdrop [number v] ::looks)
switch backdrop to (join [0] []) //second input is blank
set [backdrops v] to (backdrop [number v] ::looks)
switch backdrop to (save)

WindowsMeRules2000 wrote:

Can I make the 8th workaround guide?

modesties wrote:

(backdrop count ::looks)

Workaround:

define backdrop count
set [save v] to (backdrop [number v] ::looks)
switch backdrop to (join [0] []) //second input is blank
set [backdrops v] to (backdrop [number v] ::looks)
switch backdrop to (save)

Can do something similar if you want the number of costumes

Little_Mittle12345 wrote:

workaround for

<this sprite holding?:: sensing

when this sprite clicked
set [l v] to [1]
wait until <not <mouse down?>
set [l v] to (0)
<(l) = (1)>// sprite holding?

<this sprite holding?::sensing>

<<touching [mouse-pointer v] ?> and <mouse down?>>

-ErrorPurpl_157 wrote:

graham3078 wrote:

Could you add a workaround for “when stop sign clicked”

when green flag clicked
forever
set [Stop v] to ((Timer)+[1]) :: variables
end


when [Timer v] > (Stop)
…

when [timer v] > (0)
reset timer //nothing is allowed to be attached below

when [timer v] > (0)
do something::#888888

1080GBA wrote:

Little_Mittle12345 wrote:

workaround for

<this sprite holding?:: sensing

when this sprite clicked
set [l v] to [1]
wait until <not <mouse down?>
set [l v] to (0)
<(l) = (1)>// sprite holding?

COME ON BRUH ITS NOT THAT COMPLICATED

<this sprite holding?::sensing>

<<touching [mouse-pointer v] ?> and <mouse down?>>

dont overthink it brooooooooo

k0d3rrr wrote:

graham3078 wrote:

Could you add a workaround for “when stop sign clicked”

Such as?
-
There are two methods (with reset timer and without reset timer).

Method 1 (thanks to the Scratch Wiki)

when green flag clicked
forever
reset timer
end

when [timer v] > (0.1)
...

Method 2

when green flag clicked
forever
set [timer v] to (timer)
end

when [timer v] > (timer:: variables)
...

When project is running::events hat

Little_Mittle12345 wrote:

1080GBA wrote:

Little_Mittle12345 wrote:

workaround for

<this sprite holding?:: sensing

when this sprite clicked
set [l v] to [1]
wait until <not <mouse down?>
set [l v] to (0)
<(l) = (1)>// sprite holding?

COME ON BRUH ITS NOT THAT COMPLICATED

<this sprite holding?::sensing>

<<touching [mouse-pointer v] ?> and <mouse down?>>

dont overthink it brooooooooo

actually most people think thats the workaround it doesent work perfectly

_nix wrote:

!

1080GBA wrote:

sticky takeover when

_nix wrote:

!

when [timer v] > ((timer) - <key [space v] pressed?>

scratch workaround guide 6 wrote:

…Remember that some effects, like color, “loop” at a certain point - 100 is completely the opposite colors, 200 is back to normal, so 200 and 0 make the same result. You can use the “mod” operators block to keep the value within a specific range, as long as you know at what value it loops…

yavuz61035 wrote:

there needs to be a minor change here:

scratch workaround guide 6 wrote:

…Remember that some effects, like color, “loop” at a certain point - 100 is completely the opposite colors, 200 is back to normal, so 200 and 0 make the same result. You can use the “mod” operators block to keep the value within a specific range, as long as you know at what value it loops…

200 is actually red and 0 has no effect
you can see this by how white tints red slightly

INSERT-USER_NAME wrote:

I found a workaround for the nonexistent when <> block. I'm not sure where it would go, but I'm putting it here just in case. This is the workaround:

when [timer v] > ((timer) - <key [space v] pressed?>

_nix wrote:

INSERT-USER_NAME wrote:

I found a workaround for the nonexistent when <> block. I'm not sure where it would go, but I'm putting it here just in case. This is the workaround:

when [timer v] > ((timer) - <key [space v] pressed?>

Okay, this is actually really cool. :D

I've added it, with credits, to the top of the Events & Control section! Since it's the first custom Events block. Thank you!