Scratch

Jonathanpb · 2009-10-30 02:57:17

I'd normally say that this isn't really neccessary (you'd think "When are you going to need the semicolon?"), but there are some uses for it.

1. Word processors. In real word processors, you push keys and the characters appear. But the only things you can do on Scratch for that are the letters, numbers, and space. Very lacking for Scratch word processors (and the Backspace is a button you click!).

2. Learn-to-type programs. You won't be able to use the Shift key, and only use the letters, numbers, and space. I know that you could use the ask block, but it isn't the same. And Scratch can't sense capitalized letters from lowercase letters with the ask block.

3. Programming languages. Instead of using the chatbar to enter in code, you could use the block. And it looks nicer and it's more realistic.

Not much, but it would really be nice.

What do I want added? Well, all the characters I want available are:

"abcdefghijklmnopqrstuvqxyz1234567890!@#$%^&*()`~-_=+[{]}\|;:'",<.>/? and Enter"

(There are also suggestions for Esc, Control, Alt, Windows/Mac key, Function, F1, and F2.)

Last edited by Jonathanpb (2011-02-21 19:45:10)

Geo567 · 2009-10-30 05:47:32

True, I really want a<key[enter]pressed?> block if I want the controls tobe simple but i've allready used the space key

Jonathanpb · 2009-11-01 21:31:26

Enter! I never thought about that!

I thought of another reason for these additions...

Chrischb · 2009-11-01 21:38:47

The problem with the "Enter" idea is that it acts like you clicked the green flag. I guess the Scratch Team could disable that... it's not neccessary, after all. hmm

Jonathanpb · 2009-11-02 02:20:07

Chrischb wrote:
The problem with the "Enter" idea is that it acts like you clicked the green flag. I guess the Scratch Team could disable that... it's not neccessary, after all.

Good point!

Yes, they probably could disable that.

The-Whiz · 2009-11-02 07:02:38

Or there could be a selection under the edit menu that says, "disable enter key sensing" for it not to start the program and "enable enter key sensing".

Chrischb · 2009-11-02 23:36:02

The-Whiz wrote:
Or there could be a selection under the edit menu that says, "disable enter key sensing" for it not to start the program and "enable enter key sensing".

You really are a Whiz.
That's a good idea, and it can fit in with the Set Single Stepping stuff.

fg123 · 2009-11-03 01:38:04

Yeah! Those are great ideas. Though you would not need the !@#$%^&*() is you have numbers and shift. And you should limit the characters to the one available through mac and windows. I just wish you can input a letter in it. When you press space, it will show space, enter:enter, and so on.

Jonathanpb · 2009-11-04 22:56:38

All these ideas are great! smile

azy2 · 2009-12-14 22:33:08

[block]<when[ enter ]key pressed>[/block] thats what i want to see smile

Jonathanpb · 2009-12-14 23:56:44

The Enter key has already been covered in earlier posts. And it's in the topic post.

If you press Enter, it acts as the green flag (except for when you input something with the ask block). Maybe using Enter for the green flag could be disabled (argh, I use Enter a lot instead of clicking the green flag).

fanofcena · 2009-12-15 01:39:39

Well the control keys are harder to process due to the Character value they have as A is 65 in ascii u can build a function for this but building a function for return ;,<>etc will cause more troulbe and will probabaly result in slow down so its better if scratch stays like this for better information see the key pressed blocks programming in BYOB or source code

ThePCKid · 2009-12-15 18:09:09

Geo567 wrote:
True, I really want a<key[enter]pressed?> block if I want the controls tobe simple but i've allready used the space key

I need that for my ihunter Rapsody Scratch OS!

timetravelernick · 2011-02-20 14:10:52

<key[ shift ]pressed?> <when[ shift ]key pressed> they are like the same

scimonster · 2011-02-20 15:28:04

I agree. This person has some projects that use these, by hacking.

bbbeb · 2011-02-20 15:31:53

Jonathanpb wrote:
I'd normally say that this isn't really neccessary (you'd think "When are you going to need the semicolon?"), but there are some uses for it.

1. Word processors. In real word processors, you push keys and the characters appear. But the only things you can do on Scratch for that are the letters, numbers, and space. Very lacking for Scratch word processors (and the Backspace is a button you click!).

2. Learn-to-type programs. You won't be able to use the Shift key, and only use the letters, numbers, and space. I know that you could use the ask block, but it isn't the same. And Scratch can't sense capitalized letters from lowercase letters with the ask block.

3. Programming languages. Instead of using the chatbar to enter in code, you could use the block. And it looks nicer and it's more realistic.

Not much, but it would really be nice.

What do I want added? Well, all the characters I want available are:
"abcdefghijklmnopqrstuvqxyz1234567890!@#$%^&*()`~-_=+[{]}\|;:'",<.>/? and Enteresc, control, alt, and the mac apple key"

Added more important ones.

I didn't forget about mac users big_smile

Last edited by bbbeb (2011-02-20 15:32:29)

Jonathanpb · 2011-02-20 18:27:57

Bumped? Ooh, cool tongue

Chrischb · 2011-02-20 18:36:04

O_o bumped? It's always odd reading through my old posts...
..........................................
I still support, I guess tongue

scimonster · 2011-02-21 06:00:49

bbbeb wrote:
Jonathanpb wrote:
I'd normally say that this isn't really neccessary (you'd think "When are you going to need the semicolon?"), but there are some uses for it.

1. Word processors. In real word processors, you push keys and the characters appear. But the only things you can do on Scratch for that are the letters, numbers, and space. Very lacking for Scratch word processors (and the Backspace is a button you click!).

2. Learn-to-type programs. You won't be able to use the Shift key, and only use the letters, numbers, and space. I know that you could use the ask block, but it isn't the same. And Scratch can't sense capitalized letters from lowercase letters with the ask block.

3. Programming languages. Instead of using the chatbar to enter in code, you could use the block. And it looks nicer and it's more realistic.

Not much, but it would really be nice.

What do I want added? Well, all the characters I want available are:
"abcdefghijklmnopqrstuvqxyz1234567890!@#$%^&*()`~-_=+[{]}\|;:'",<.>/? and Enter esc, control, alt, and the Mac apple key/Windows Logo key"
Added more important ones.

I didn't forget about mac users

Another one-for windows. smile

ScratchReallyROCKS · 2011-02-21 11:10:29

I've been thinking about this for a long time. It would be very helpful. I think they should also add a (key pressed) reporter block, so you don't have to use a long string of booleans for typing without the ask block.

BTW:

Jonathanpb wrote:
and the Mac apple key

Could you please fix this? It's called the "command" key.

kayybee · 2011-02-21 12:41:41

Yes, truly on some macs there is no "apple" key, it's command.

Unless you're talking about option-shift-k.

Also, function Kay, f1, f2...

Jonathanpb · 2011-02-21 19:43:36

ScratchReallyROCKS wrote:
Could you please fix this? It's called the "command" key.

Okay tongue

kayybee wrote:
Also, function Kay, f1, f2...

Okay tongue

Last edited by Jonathanpb (2011-02-21 19:44:18)

Scratch

archived forums

#1 2009-10-30 02:57:17

More for the [When ___ key pressed] and <if key ___ pressed> blocks.

#2 2009-10-30 05:47:32

Re: More for the [When ___ key pressed] and <if key ___ pressed> blocks.

#3 2009-11-01 21:31:26

Re: More for the [When ___ key pressed] and <if key ___ pressed> blocks.

#4 2009-11-01 21:38:47

Re: More for the [When ___ key pressed] and <if key ___ pressed> blocks.

#5 2009-11-02 02:20:07

Re: More for the [When ___ key pressed] and <if key ___ pressed> blocks.

Chrischb wrote:

#6 2009-11-02 07:02:38

Re: More for the [When ___ key pressed] and <if key ___ pressed> blocks.

#7 2009-11-02 23:36:02

Re: More for the [When ___ key pressed] and <if key ___ pressed> blocks.

The-Whiz wrote:

#8 2009-11-03 01:38:04

Re: More for the [When ___ key pressed] and <if key ___ pressed> blocks.

#9 2009-11-04 22:56:38

Re: More for the [When ___ key pressed] and <if key ___ pressed> blocks.

#10 2009-12-14 22:33:08

Re: More for the [When ___ key pressed] and <if key ___ pressed> blocks.

#11 2009-12-14 23:56:44

Re: More for the [When ___ key pressed] and <if key ___ pressed> blocks.

#12 2009-12-15 01:39:39

Re: More for the [When ___ key pressed] and <if key ___ pressed> blocks.

#13 2009-12-15 18:09:09

Re: More for the [When ___ key pressed] and <if key ___ pressed> blocks.

Geo567 wrote:

#14 2011-02-20 14:10:52

Re: More for the [When ___ key pressed] and <if key ___ pressed> blocks.

#15 2011-02-20 15:28:04

Re: More for the [When ___ key pressed] and <if key ___ pressed> blocks.

#16 2011-02-20 15:31:53

Re: More for the [When ___ key pressed] and <if key ___ pressed> blocks.

Jonathanpb wrote:

#17 2011-02-20 18:27:57

Re: More for the [When ___ key pressed] and <if key ___ pressed> blocks.

#18 2011-02-20 18:36:04

Re: More for the [When ___ key pressed] and <if key ___ pressed> blocks.

#19 2011-02-21 06:00:49

Re: More for the [When ___ key pressed] and <if key ___ pressed> blocks.

bbbeb wrote:

Jonathanpb wrote:

#20 2011-02-21 11:10:29

Re: More for the [When ___ key pressed] and <if key ___ pressed> blocks.

Jonathanpb wrote:

#21 2011-02-21 12:41:41

Re: More for the [When ___ key pressed] and <if key ___ pressed> blocks.

#22 2011-02-21 19:43:36

Re: More for the [When ___ key pressed] and <if key ___ pressed> blocks.

ScratchReallyROCKS wrote:

kayybee wrote:

Board footer

More for the [When _ key pressed] and <if key _ pressed> blocks.

Re: More for the [When _ key pressed] and <if key _ pressed> blocks.

Re: More for the [When _ key pressed] and <if key _ pressed> blocks.

Re: More for the [When _ key pressed] and <if key _ pressed> blocks.

Re: More for the [When _ key pressed] and <if key _ pressed> blocks.

Re: More for the [When _ key pressed] and <if key _ pressed> blocks.

Re: More for the [When _ key pressed] and <if key _ pressed> blocks.

Re: More for the [When _ key pressed] and <if key _ pressed> blocks.

Re: More for the [When _ key pressed] and <if key _ pressed> blocks.

Re: More for the [When _ key pressed] and <if key _ pressed> blocks.

Re: More for the [When _ key pressed] and <if key _ pressed> blocks.

Re: More for the [When _ key pressed] and <if key _ pressed> blocks.

Re: More for the [When _ key pressed] and <if key _ pressed> blocks.

Re: More for the [When _ key pressed] and <if key _ pressed> blocks.

Re: More for the [When _ key pressed] and <if key _ pressed> blocks.

Re: More for the [When _ key pressed] and <if key _ pressed> blocks.

Re: More for the [When _ key pressed] and <if key _ pressed> blocks.

Re: More for the [When _ key pressed] and <if key _ pressed> blocks.

Re: More for the [When _ key pressed] and <if key _ pressed> blocks.

Re: More for the [When _ key pressed] and <if key _ pressed> blocks.

Re: More for the [When _ key pressed] and <if key _ pressed> blocks.

Re: More for the [When _ key pressed] and <if key _ pressed> blocks.