Scratch

blue80070 · 2012-09-05 13:04:47

I know the workaround is very easy,

Wait until <<mouse down?>and<touching [mouse pointer v]?>>

But if you are doing this a lot, it can take a while, so it we quicker to have when sprite clicked as a boolean block, eg:

Wait until  <[sprite] clicked>

scimonster · 2012-09-05 13:11:18

Something that simple doesn't need a new block. hmm

zammer990 · 2012-09-05 13:58:39

I just use the "duplicate" function if I'm going to use it a lot.

BirdByte · 2012-09-05 14:02:22

The above 2 posts +1

sonicfan12p · 2012-09-05 14:45:17

In 2.0, you can byob that does this. Just define it with that script.

scimonster · 2012-09-05 15:02:01

sonicfan12p wrote:
In 2.0, you can byob that does this. Just define it with that script.

2.1, or maybe even later. 2.0 won't support custom booleans or reporters. sad

xJira · 2012-09-05 15:26:01

I support. I know there is an easy other way, still I always missed a block like that.
And isn't it right that you can just definde stack-blocks with the new 2.0-function? thought I read it somewhere...

sonicfan12p · 2012-09-05 15:34:24

It won't support another block with booleans and reporters in them? It wouldn't support the full

wait until <<mouse down?> and <touching [mouse v]?>>

I tried it in the beta, or alpha, whichever, and it seemed to work.

Mokat · 2012-09-05 17:49:46

The Scratch Team hardly ever accepts suggestions with easy workarounds.

dvd4 · 2012-09-06 20:06:04

scimonster wrote:
Something that simple doesn't need a new block.

OverPowered · 2012-09-06 22:29:23

But the workaround isn't perfect... If the mouse is down and passes over the sprite, ie while dragging something, then this would trigger...
I know that there's another workaround...

when gf clicked
forever if <(clicked?) = [yes]>
set [clicked v] to [no]
do stuff

when ClickMe clicked
set [clicked v] to [yes]
end script

... but this boolean block would allow for easier (and one-script) perfect "click" sensing, which would be really nice for multipupose buttons. smile

RedRocker227 · 2012-09-07 03:13:05

That workaround isn't an exact workaround

jji7skyline · 2012-09-07 03:15:32

I guess none of the workarounds are perfect.

jontmy00 · 2012-09-07 04:45:15

And if the sprite is at the back and hidden, it still triggers.

BirdByte · 2012-09-07 06:59:51

Perfect workaround, but it'll only substitute for a wait until:

set [cl v] to [0]
repeat until <(cl) =  [1]>
 wait until <not <mouse down?>>
 wait until <mouse down?>
 if <touching [mouse-pointer v]?>
  set [cl v] to [1]
 end
end

Last edited by BirdByte (2012-09-07 07:00:19)

Scratch

archived forums

#1 2012-09-05 13:04:47

When sprite clicked as a boolean block

#2 2012-09-05 13:11:18

Re: When sprite clicked as a boolean block

#3 2012-09-05 13:58:39

Re: When sprite clicked as a boolean block

#4 2012-09-05 14:02:22

Re: When sprite clicked as a boolean block

#5 2012-09-05 14:45:17

Re: When sprite clicked as a boolean block

#6 2012-09-05 15:02:01

Re: When sprite clicked as a boolean block

sonicfan12p wrote:

#7 2012-09-05 15:26:01

Re: When sprite clicked as a boolean block

#8 2012-09-05 15:34:24

Re: When sprite clicked as a boolean block

#9 2012-09-05 17:49:46

Re: When sprite clicked as a boolean block

#10 2012-09-06 20:06:04

Re: When sprite clicked as a boolean block

scimonster wrote:

#11 2012-09-06 22:29:23

Re: When sprite clicked as a boolean block

#12 2012-09-07 03:13:05

Re: When sprite clicked as a boolean block

#13 2012-09-07 03:15:32

Re: When sprite clicked as a boolean block

#14 2012-09-07 04:45:15

Re: When sprite clicked as a boolean block

#15 2012-09-07 06:59:51

Re: When sprite clicked as a boolean block

Board footer