What if Scratch could be modified so users could able to use ‘hotkeys’ to make blocks? This would mean that you either press a letter or number key, and Scratch automatically puts a block next in your script. This would be much faster, especially for complicated mathematics/formulae. It would also mean that the scripts would be a lot neater, and users wouldn't need to drag block around to where they need to go. I acknowledge that using hotkeys might take some learning, but it can easily be done, and would improve the speed at which projects could be made.

For example, to create the script:

when green flag clicked
forever
if <(([x] * [y]) + [z]) = [a]> then
say [Yay!!]
end
end

a user would press, W; F; I; =; +; *; x; y; z; a; S; Yay!!
and that's it. A lot quicker and neater.
Please give me feedback on if this is a good idea, and how this could be achieved.
Sorry if this won't work for whatever reason.

Scratch on!

How would it know where to place blocks?

Sigton

Hmmm… I can see it being useful, but have the same question as Sigton. Would it take it to the opening closest to your mouse? What if you were typing a list and had many semi-colons for some reason? Would there be an option to turn it off and on? Easily accessible guides/tutorials?

Sigton wrote:

How would it know where to place blocks?

Sigton

I imagine there would be a sort of “cursor” at the end of the last script you changed by default. It could be moved with the arrow keys or with the mouse. Hat blocks would always be a new script although I don't know exactly where it would put them.

As for where it could go, I can see it going to the top-left corner; where all the scripts go upon duplication or using Undelete.
I can see myself using this in the future quite often; maybe make it so that, when you right-click, there'll be an option saying “Set as hotkey”, which then opens up a text box with a one-character limit. After you type in the character, you can use that hotkey with maybe SHIFT+CTRL+Assigned Hotkey? If so, that would be quite useful for me, as I'd be able to instantly insert any block combination that I'd need at any time.

Yeah, I think it could be turned off.
I think it would be easiest if each new letter filled in the earliest open space. For example, if you make a

([A] +[B])

block, then whatever you type will fill in A, then the next thing will fill in B.
This may mean that people will have to reorder their code somewhat, but people would get used to it.
If you make:

forever
if <([A] + [B]) = [C]> then
say [D]
end
end

You would type F (for forever)); I (for if); =; +; A; B; C; S (for say); D.
Whenever ; or is pressed, it would switch to the next ‘open’ block.

I can see an inconsistency here already.

In the first post, you type letters and it inserts variable reporters, and in the last post you type letters and it enters them as strings. There would need to be some way to distinguish between the two (maybe d, v, variable name; for a variable reporter?) and also distinguish strings from the other hotkeys.

stickfiregames wrote:

I can see an inconsistency here already.

In the first post, you type letters and it inserts variable reporters, and in the last post you type letters and it enters them as strings. There would need to be some way to distinguish between the two (maybe d, v, variable name; for a variable reporter?) and also distinguish strings from the other hotkeys.

Sorry about this. Maybe someone could press SHIFT-letter for a string, and ALT-letter for a variable.
This was only an idea, and this is my only suggestion I've ever made.
Thanks anyway, though

stickfiregames wrote:

I can see an inconsistency here already.

In the first post, you type letters and it inserts variable reporters, and in the last post you type letters and it enters them as strings. There would need to be some way to distinguish between the two (maybe d, v, variable name; for a variable reporter?) and also distinguish strings from the other hotkeys.

No, there totally wasn't an inconsistency, and I totally haven't just edited my first post.

just kidding

Bumpity Bumpity Buuuuuuuuuuuump!!!

Bump!

Please only bump every 24 hours, and if your topic is off the first page.

I no support since it seems very complicated, and the way that we use blocks now is fine.

duckboycool wrote:

Please only bump every 24 hours, and if your topic is off the first page.

I no support since it seems very complicated, and the way that we use blocks now is fine.

Sorry.

Semi-Support.

I myself would find this extremely useful. But there is one problem.

Unless if I read the OP wrong (and other posts) you're suggesting this for all blocks?

In that case I believe there are too many Scratch Blocks to fit on a keyboard? Correct me if I'm wrong.

Plus you'd have to memorize a specific key to get that block. But I'm sure that's a minor problem, especially if you're a constant scratcher.

Actually… while typing this I'll decided to change to full support…

Sorry that I'm that indecisive. XD

I think you should be able to turn it on and off, and when on, have settings for which blocks would be assigned to which hotkey. For example, by default, you'd have no blocks as the hotkey. However, if you assigned a certain hotkey to a script or group of blocks with a right-click dropdown, then you'd be able to make it instantly appear by pressing SHIFT+Hotkey.

Thanks for the support. Yeah, I think that maybe you could press “SHIFT-ALT-H” to enable/disable hotkeys.
My idea is that you press a letter to select the class of block (event, control, motion, etc.) and then another letter to choose the block. Yes, it would take some memorising, but I think it would be worth it.

For what it's worth, you might be interested in learning about Snap!'s keyboard editing features. Those are explained in the official Snap! Reference Manual, section D. under chapter X. (Page 86, currently; you could also just do a control-F and search for “Keyboard Editing” in the document.) They might be interesting!

_nix wrote:

For what it's worth, you might be interested in learning about Snap!'s keyboard editing features. Those are explained in the official Snap! Reference Manual, section D. under chapter X. (Page 86, currently; you could also just do a control-F and search for “Keyboard Editing” in the document.) They might be interesting!

Ok! Thanks!

Bump!