simulate key [] pressed
simulate key [] pressed for () seconds
simulate key [] pressed until <>

This would allow your program to run any cap or sensing block that detects key pressing to run, without user interaction.
This would be in the sensing category.

Would it press the key as if you pressed it or just run the cap blocks?

rh_junr wrote:

Would it press the key as if you pressed it or just run the cap blocks?

I would act as though you pressed the key
(Basically running all cap blocks and sensing blocks)
It would not actually move your keyboard

So ghost pressing?

Why would you want this again?
Also couldn't you just use broadcasts?:

broadcast [ v]

when I receive [ v]
Do press stuff here

MathlyCat wrote:

So ghost pressing?

Why would you want this again?
Also couldn't you just use broadcasts?:

broadcast [ v]

when I receive [ v]
Do press stuff here

Yes, but if you have a really long script, and you don't want to do it twice, one for

when [a] key pressed

AND one for

when I receive [message]

If the script is really long, having two might lag your project.

jtmit wrote:

simulate key [] pressed
simulate key [] pressed for () seconds
simulate key [] pressed until <>

This would allow your program to run any cap or sensing block that detects key pressing to run, without user interaction.
This would be in the sensing category.

Couldn't you just do this?

when green flag clicked
forever
wait until <<key [ v] pressed?> or <(variable) = [1]>>
do le stuff
end

and then somewhere else

when green flag clicked
forever
if <some condition> then
set [ variable] to [1]

else

set [variable] to [0]
end
end

or something like that. this was done on the fly so there could be a few bugs.

JBGT wrote:

jtmit wrote:

simulate key [] pressed
simulate key [] pressed for () seconds
simulate key [] pressed until <>

This would allow your program to run any cap or sensing block that detects key pressing to run, without user interaction.
This would be in the sensing category.

Couldn't you just do this?

when green flag clicked
forever
wait until <<key [ v] pressed?> or <(variable) = [1]>>
do le stuff
end

and then somewhere else

when green flag clicked
forever
if <some condition> then
set [ variable] to [1]

else

set [variable] to [0]
end
end

or something like that. this was done on the fly so there could be a few bugs.

I guess, this was just meant to make it easier. What you show is definitely possible.

So it would “stimulate” key presses? Would this work on only that project or would it send across your entire computer? Because making a scratch project to help me make viruses make more batch files could bring scratch to a whole new level

SuperHal989 wrote:

So it would “stimulate” key presses? Would this work on only that project or would it send across your entire computer? Because making a scratch project to help me make viruses make more batch files could bring scratch to a whole new level

No, it would only affect the current scratch project.

I don't think this is necessary, it's pretty easy to just duplicate scripts (Right click>duplicate, in case you were wondering) to make use of Mathlycat's workaround. If you really don't want to make a few extra clicks, you can always make a custom block and just use that.

Custom blocks serve your purpose (for most (event-based) purposes):

when [a v] key pressed
my action

forever // every 5 seconds, "simulate" pressing the A key
  my action
  wait (5) secs
end

define my action
play drum (1 v) for (0.25) beats

If your project doesn't happen to be event-based like that you can use variables.

when gf clicked
set [simulated right key pressed? v] to [0]
forever
  if <<key [right arrow v] pressed?> or <(simulated right key pressed?) = [1]>> then
    set [right key pressed? v] to [1]
  else
    set [right key pressed? v] to [0]
  end
end

when flag clicked
forever
  if <(right key pressed?) = [1]> then
    move (5) steps
  end
end

when flag clicked
forever // every 5 seconds, "simulate" pressing the right key for 1 second
  wait (5) secs
  set [simulated right key pressed? v] to [1]
  wait (1) secs
  set [simulated right key pressed? v] to [0]
end

jtmit wrote:

JBGT wrote:

jtmit wrote:

simulate key [] pressed
simulate key [] pressed for () seconds
simulate key [] pressed until <>

This would allow your program to run any cap or sensing block that detects key pressing to run, without user interaction.
This would be in the sensing category.

Couldn't you just do this?

when green flag clicked
forever
wait until <<key [ v] pressed?> or <(variable) = [1]>>
do le stuff
end

and then somewhere else

when green flag clicked
forever
if <some condition> then
set [ variable] to [1]

else

set [variable] to [0]
end
end

or something like that. this was done on the fly so there could be a few bugs.

I guess, this was just meant to make it easier. What you show is definitely possible.

It's so much easier with variables and broadcasts rather than trying to fit your blocks into script.
Really, it's better for Scratcher's to learn/teach themselves how to produce such script, because in reality, other programming languages don't always have specific functions that simulate a button press.