The blocks I'm suggesting are:

emulate (space v) key press and wait::events

emulate (space v) key press::events

When those blocks is clicked (or hit in the code), it will trigger all of the “key pressed” blocks of a certain key.

I'm also suggesting this block:

emulate cursor click at x: () y: ()::events

This would do exactly what it says - simulate a mouse click in a set position.

These blocks, specifically the first few, would make testing easier and would be easy to activate code while a game is playing WITHOUT having to deal with broadcasting.

The other dropdowns would be the other keys. Also, note that the dropdown is OVAL instead of rectangular, for putting in join blocks to make enter, /, <, >, etc. keys.

Support!

removed

I support. This would be good for testing without having to edit large amounts of code.

If it is implemented however I recommend you change the text to.

Trigger event key (space v) press

-EmeraldThunder- wrote:

I support. This would be good for testing without having to edit large amounts of code.

If it is implemented however I recommend you change the text to.

Trigger event key (space v) press

Sure, thanks.

misteray wrote:

Support!

Please tell us why you support.

-EmeraldThunder- wrote:

I support. This would be good for testing without having to edit large amounts of code.

If it is implemented however I recommend you change the text to.

Trigger event key (space v) press

An even better name might be

simulate (space v) key press :: control

I think it should press the key for one frame, so “key pressed?” blocks that run in the next frame would return true. There could also be blocks blocks that press and release the key:

simulate (space v) key press start :: control
simulate (space v) key press end :: control

Maximouse wrote:

-EmeraldThunder- wrote:

I support. This would be good for testing without having to edit large amounts of code.

If it is implemented however I recommend you change the text to.

Trigger event key (space v) press

An even better name might be

simulate (space v) key press :: control

I think it should press the key for one frame, so “key pressed?” blocks that run in the next frame would return true. There could also be blocks blocks that press and release the key:

simulate (space v) key press start :: control
simulate (space v) key press end :: control

What category do you suggest? I was thinking about events, but you're saying control.
Also, what do you think of the hat block?

so what about

Trigger event key (space v) press and wait :: events

scratchastroLOL wrote:

so what about

Trigger event key (space v) press and wait :: events

Compromises; great idea!

An even better name might be

key down (space v) key press :: control
key up (space v) key press :: control
press key (space v) for () seconds :: control

Chiroyce wrote:

An even better name might be

key down (space v) key press :: control
key up (space v) key press :: control
press key (space v) for () seconds :: control

Maybe, but you might want to add a simulate in there like so:

simulate key down (space v) key press :: control
simulate key up (space v) key press :: control
simulate press key (space v) for () seconds :: control

These are getting a bit long, though, but that's another suggestion. (To make it so you can scroll either way on the blocks palette).

Cool idea for testing, especially if the key isn't working, or you want to make a mobile version
Then again:

when [..v] key pressed
Simulate [.. v]

1Oaktree2 wrote:

Then again:

when [..v] key pressed
Simulate [.. v]

You can do that with broadcasts already.

han614698 wrote:

the2000 wrote:

You can do that with broadcasts already.

the2000, do you support or not. What are your ideas, especially about the hat block.

I have the right to remain with my stance on the suggestion unstated.

Anyway, this would be useful, but I'm not sure if it would belong in the main palette. Since there already is an extension with only two blocks (Translate IIRC) I don't think that it would be too out of place to make this an extension. Or they could just be hidden blocks, IDK. This could make an easy way to create mobile controls, which would be nice.

the2000 wrote:

han614698 wrote:

the2000 wrote:

You can do that with broadcasts already.

the2000, do you support or not. What are your ideas, especially about the hat block.

I have the right to remain with my stance on the suggestion unstated.

Anyway, this would be useful, but I'm not sure if it would belong in the main palette. Since there already is an extension with only two blocks (Translate IIRC) I don't think that it would be too out of place to make this an extension. Or they could just be hidden blocks, IDK. This could make an easy way to create mobile controls, which would be nice.

Ok, thanks. Do you like the hat block?

Can you change the title to
“Key press emulation blocks” or something more technically understandable ?

han614698 wrote:

the2000 wrote:

Anyway, this would be useful, but I'm not sure if it would belong in the main palette. Since there already is an extension with only two blocks (Translate IIRC) I don't think that it would be too out of place to make this an extension. Or they could just be hidden blocks, IDK. This could make an easy way to create mobile controls, which would be nice.

Ok, thanks. Do you like the hat block?

Seems like it would sorta ruin the point to differentiate between real and simulated inputs? You could just use broadcasts for every purpose that the hat would come in handy for. I'm not sure why it's a rounded drop-down, either.