Title explains it all. There should be an option to make scripts that function when any key is clicked, like this:

when [any v] key pressed // I'm not sue if it should be a the top or bottom of the dropdown, or if it should be default.

<key [any v] pressed?> // ditto

Any other ideas?
I got rid of the supporter count.

Support, very easy to add but would have a lot of uses.

Too unclear. Would it include JUST the options in the dropdown or more options like shift? Would the mouse down count?
BUT, it would be convienient.
Support +0.5.

PaganoLeo10 wrote:

Too unclear. Would it include JUST the options in the dropdown or more options like shift? Would the mouse down count?
BUT, it would be convienient.
Support +0.5.

In my mind, I didn't think of mouse keys. However, that may be a good idea… maybe you could chose to include mouse click or not? Also, I was not planning on using shift. It has other uses (e.g. turbo mode) and that may not work.
Does that clear things up?
Full Support?

Support!
Also another related idea:

(last key pressed::sensing)//which could be used with this:
<[ v] is a [letter v]::sensing>
<[ v] is a [number v]::sensing>
<[ v] is a [key(shift ect) v]::sensing>
<and more...::sensing>

Zappy1333 wrote:

Support!
Also another related idea:

(last key pressed::sensing)//which could be used with this:
<[ v] is a [letter v]::sensing>
<[ v] is a [number v]::sensing>
<[ v] is a [key(shift ect) v]::sensing>
<and more...::sensing>

Thanks for the support and ideas! However, for the convenience of this topic, could you put those ideas in a new topic? Don't get me wrong, I think those are very good ideas. However, I just think that would make more sense. Thanks!
PS: Put me down for support on the those ideas. The reporters could simplify a lot of things. Also, be aware that people will tell you to work around it with this:

when [x v] key pressed
set [last key pressed v] to [x ]

Letsgopitt wrote:

Title explains it all. There should be an option to make scripts that function when any key is clicked, like this:

when [any v] key pressed // I'm not sue if it should be a the top or bottom of the dropdown, or if it should be default.

<key [any v] pressed?> // ditto

Any thoughts, please reply/support! I am making a text engine and it would be good to have a script like this to simplify things:

when [any v] key pressed
stamp

Thanks, and Scratch On!

SUPPORT!

Bump.
I think this is very easy to implement, so any other supporters?

Support!

support, along with more keys in

when [ v] key pressed
<key [ v] pressed?>

like: !@#$%^&*()_+~`-=,./<>?;':"{}

Semi-support. I would like

(key pressed? :: sensing)

because you can do

if <not <( key pressed? :: sensing) = [ ]>> then
    ... :: grey
end

Support

Bump.

Bumpity bomb.

Support.

+0.5 support. Although it could be replicated with some time, it might interfere with other key pressed blocks.

gigapouch wrote:

+0.5 support. Although it could be replicated with some time, it might interfere with other key pressed blocks.

How would it conflict with other commands? Could you give me an example?

Letsgopitt wrote:

gigapouch wrote:

+0.5 support. Although it could be replicated with some time, it might interfere with other key pressed blocks.

How would it conflict with other commands? Could you give me an example?

If you had other key pressed blocks and you pressed one of those keys accidentally, the command that block would trigger would also trigger with the if any key pressed command. It may make the editor crash.

gigapouch wrote:

Letsgopitt wrote:

gigapouch wrote:

+0.5 support. Although it could be replicated with some time, it might interfere with other key pressed blocks.

How would it conflict with other commands? Could you give me an example?

If you had other key pressed blocks and you pressed one of those keys accidentally, the command that block would trigger would also trigger with the if any key pressed command. It may make the editor crash.

…????? No it wouldn't.

djdolphin wrote:

gigapouch wrote:

Letsgopitt wrote:

gigapouch wrote:

+0.5 support. Although it could be replicated with some time, it might interfere with other key pressed blocks.

How would it conflict with other commands? Could you give me an example?

If you had other key pressed blocks and you pressed one of those keys accidentally, the command that block would trigger would also trigger with the if any key pressed command. It may make the editor crash.

…????? No it wouldn't.

I don't think that would happen, but both commands would go at the same time. Also, they would be used in different circumstances.