Full support! I think this would be a really nice addition, super useful and would make it quicker and easier.

oops it didn't show the first time, I posted twice sorry

ResExsention wrote:

CatsUnited wrote:

WindOctahedron wrote:

-snip-

Oh yeah I forgot it can't be “confusing for new users”.
I'll still support this suggestion though because it's a better (and probably still faster even without my suggestion) way to select a key for the <key pressed> block, and it looks a lot better visually.

I agree… How can this possibly be complicated?

You press Shift, and “Sorry, but this key is not compatible.” shows up.
You press Tab, and “Sorry, but this key is not compatible.” shows up.
You press Backspace, and “Sorry, but this key is not compatible.” shows up.
I meant that if this happened every time you tried a key, it would waste time instead of visually telling you which keys won't work.
Statement improvement: this is also not a good idea for tablet users, since you* have to wait before a real keyboard appears (as far as my own experience goes), but you could just tap and select the key without the delay. I now edited the post that I link to with “see this post” by writing there the “statement improvement”.
*Okay, I admit it: it works at least for me.

Just make it so hovering over an unsupported grayed out key gives no result, this way the kids won't have some foreign thing popping up.

I agree. I imagine now that when one hovers over a supported key, it is highlighted, but hovering over an unsupported key won't result in the key's highlight.

Also, I'm slightly offended by the statement about how the stereotype of new Scratchers was that they were young. Do I really have to promote myself?

No, you don't. You are one of those exceptions who doesn't want to press that button (because you want to hold the record for “highest amount of posts by a New Scratcher” (I think)).

Bump.

Bump.

Bump.

Support. But I think that it would save more time if you can press the key on your real keyboard.

Bump.

Bump.

Bomp (2nd page)

support! it would look better, to match the

play note ( v) for (0.5) beats

and

point in direction ( v)

blocks' dropdowns

Bump.

Support

ThatOneWeirdDude wrote:

Support

Please give reasons.

Support, it would save time and make things way easier and less time consuming, but there should be options for which kind of keyboard someone is using(like QWERTY) and you would be able to do what the quote below says.

Robby_Blue wrote:

Support. But I think that it would save more time if you can press the key on your real keyboard.

Bump.

Support, it'd be faster, neater, and less annoying.

Support.

It would make things way easier, especially for people who have problems with moving their hands properly. I would also prefer this method since I do not want to go on an endless scrolling session everytime I use a mere Scratch block.

ResExsention wrote:

Support.

It would really save time.

Would the incompatible keys be grayed out? And what about the numpad? Not all keyboards have a number pad.

I support this because, yes, it would definitely save time. The only issue is that I believe some different countries have different keyboards, and I've been on and off Russian and English language on here, and I've noticed the

<key [ v] pressed?>

and

when [ v] key pressed

blocks only use the QWERTY letters, so having a keyboard would probably be confusing for other countries.

Support! It will save a lot of time.