powercon5 wrote:

Code_Spawner wrote:

I support. This would make things so much easier - instead of doing

when green flag clicked
forever
if <> then
<key [a] pressed?>
set [text] to (join (foo) [a])
end
end

and then repeat that 25 more times. Very good idea!

Especially with 3.0, there's a much easier way.
You can use something like this

define Key pressed
set [Key pressed v] to []
set [i v] to [0]
repeat (length of [ qwertyuiopasdfghjklzxcvbnm1234567890])
change [i v] by (1)
if <key (letter (i) of [ qwertyuiopasdfghjklzxcvbnm1234567890]) pressed?> then
set [key pressed v] to (letter (i) of [ qwertyuiopasdfghjklzxcvbnm1234567890])
stop [this script v]

end

end

when green flag clicked
forever
if <key [ delete] pressed?> then
(your stuff)
end
end

when green flag clicked
forever
if <key [ delete] pressed?> then
your stuff
end
end

IvanChan3 wrote:

I mean:

when green flag clicked
forever
if <key [ delete] pressed?> then
your stuff
end
end

Sheep_maker wrote:

What if multiple keys are pressed? What would it report?
Say the key “r” was pressed. Obviously, the block would report “r”
But if both “r” and “g” are pressed, the block wouldn't be “r” anymore, so

<(keys pressed::sensing)=[r]>

Wouldn't work even though the r key is being pressed.

And how'll the cursor keys, enter/return, backspace/delete, delete/delete, and ctrl/command/shift/alt/option/etc. be reported via this block?

<(keys pressed::sensing) contains [r]?:: operators>

Sheep_maker wrote:

This wouldn't work:

<(keys pressed::sensing)=[h]>

if “h” and “k” were both being pressed, assuming that first class lists aren't coming with this block. And what format would the list be: “hk” “h k” “h, k” etc.?

What order would these keys be listed in? How would backspace, enter, tab, and shift/ctrl/alt/etc. be reported? Would the symbols be reported as well? How would it report shift+H? What if caps lock was on? etc. etc. etc.

However first class lists would make everything easier and so

theonlygusti wrote:

Ideally, Scratch would implement first class lists and then we could have this block report a list of the keys pressed, and it would look like this:

if <(keys pressed :: sensing) contains [W]?> then
end

or we could change the block to

(last key pressed::sensing)

when [any v] key pressed
set [charlist v] to [`~1!2@3#4$5%6^7&8*9(0)-_=+qwertyuiop[{\]}\|asdfghjkl;:'"zxcvbnm,<.>/?]
set [loop v] to [0]
repeat (length of (charlist))
change [loop v] by [1]
if <key (letter (loop) of (charlist)) pressed> then
set [input v] to (join (input) (letter (loop) of (charlist))
end
end

when [any v] key pressed
set [charlist v] to [`~1!2@3#4$5%6^7&8*9(0)-_=+qwertyuiop[{\]}\|asdfghjkl;:'"zxcvbnm,<.>/?]
set [loop v] to [0]
repeat (length of (charlist))
change [loop v] by [1]
if <key (letter (loop) of (charlist)) pressed> then
set [input v] to (join (input) (letter (loop) of (charlist))
end
end

(join [ctrl] [])

(join [control] [])

PizzaAddict4Life wrote:

SUPPORT!. I have recently wanted to make it so that if you pressed the “ctrl” key it would do something, using this workaround:

(join [ctrl] [])

(join [control] [])

But neither of those work. So I would want to know what the control key is listed as so I can do that.

FULL SUPPORT!

<last key pressed>  :: sensing

(key pressed)

scratch0maker0 wrote:

Ok, I want a block that senses which key was pressed and returns that key.
like this:

if <(key pressed:: sensing) = [r]> then
your stuff :: grey
end

It would be helpful in touch typing projects.

(key pressed)

when green flag clicked
forever
if <key [whatever letter you want v] pressed?> then
set [key pressed v] to [whatever letter you want]

scratch0maker0 wrote:

Suppose I have a custom block called text ().
Instead of this,

when [a v] key pressed
text (a) :: custom
when [b v] key pressed
text  (b):: custom
when [c v] key pressed
text  (c) :: custom

and on... :: grey

I can do this:

when green flag clicked
forever
if <key [any key v] pressed?> then
text (key pressed :: sensing) :: custom
end
end

fdreerf wrote:

Bump after this topic has been merged.