DangerPuppy10 wrote:

I mean, this would be very confusing. I still don't quite understand this.

Ok, so; this would simulate a button being pressed. And this would also simulate a mouse being at a certain point. But, I'm still confused. Why would we need this?

han614698 wrote:

bump

han614698 wrote:

han614698 wrote:

bump

han614698 wrote:

han614698 wrote:

han614698 wrote:

bump

han614698 wrote:

(#147)

han614698 wrote:

han614698 wrote:

han614698 wrote:

bump

doggy_boi1 wrote:

(#149)
Im not reading through 8 pages of discussion, so i probably missed something but, why not just click at xy yourself or press the arrow key? And for mobile support, why not just use broadcasts?

han614698 wrote:

doggy_boi1 wrote:

(#149)
Im not reading through 8 pages of discussion, so i probably missed something but, why not just click at xy yourself or press the arrow key? And for mobile support, why not just use broadcasts?

It's mainly for testing. The clicking was the sub-suggestion, the main one was emulating key presses for mobile devices - saves a lot of time with broadcasts, specifically for platformers.

<mouse down?>
<(mouse down) = [1]>

<touching [mouse-pointer v] ?>
<touching [mouse-pointer-emulated v] ?>

point in direction/go to/glide (1) secs to [mouse-pointer v]::motion
point in direction/go to/glide (1) secs to [mouse-pointer-emulated v]::motion

mouse x/y::sensing reporter
([x/y v] of [mouse-pointer-emulated v])

move mouse pointer to x: (x) y: (y)::#0080ff
go to x: (x) y: (y)

click::#0080ff
click::my blocks
define click
set [mouse down v] to [1]
wait (0) secs
set [mouse down v] to [0]

cake__5 wrote:

big snip

BigNate469 wrote:

cake__5 wrote:

big snip

But that's a lot of work, especially in larger projects where it may not be immediately obvious where the key sensing blocks are.

I agree, this would be useful for testing (and playing) projects on mobile devices, as well as porting projects to mobile devices as you can simply emulate a keypress rather than find every instance of a key sensing block or hat block and replace it with messages and variables.

cake__5 wrote:

BigNate469 wrote:

cake__5 wrote:

big snip

But that's a lot of work, especially in larger projects where it may not be immediately obvious where the key sensing blocks are.

I agree, this would be useful for testing (and playing) projects on mobile devices, as well as porting projects to mobile devices as you can simply emulate a keypress rather than find every instance of a key sensing block or hat block and replace it with messages and variables.

its called editing the json file :)