How can I detect key input AND letter case? I've tried using sprite costumes but it only returns lowercase, never uppercase. Is this not possible using costumes?

when [any v] key pressed
set [Output key v] to ()
if <key [any v] pressed?> then
switch costume to [1 v]
repeat (110)
if <key (costume [name v]::looks) pressed> then 
set [Output key v] to (costume [name v]::looks)
stop [this script v]
else
next costume
end
end
end

i believe the problem is that the key pressed block is NOT case-sensitive. i'm not sure if it's actually possible to get case-sensitive inputs in scratch, barring usage of the ask block, which is obviously not ideal. there's also no method of detecting the shift key so you wouldn't be able to pick up capitals that way either.

MultiTasker801 wrote:

i believe the problem is that the key pressed block is NOT case-sensitive. i'm not sure if it's actually possible to get case-sensitive inputs in scratch, barring usage of the ask block, which is obviously not ideal. there's also no method of detecting the shift key so you wouldn't be able to pick up capitals that way either.

Okay. I'll look more into it but you're probably right.

But if you can detect a letter and detect if it is lower case then if it is a letter and not lower case you can detect upper case! The method using costumes can easily be modified to detect upper case instead - instead of having a set of costumes abc… you have costumes ABC…..

Really don't see the problem.

deck26 wrote:

Really don't see the problem.

even if you can get specific case letters, you run into a problem when you try to detect them as inputs because none of the input detecting blocks:

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

are case sensitive. case sensitive input detection in vanilla scratch is impossible. case closed

Scratch costume names are case sensitive, but the <key … pressed> block is not case sensitive.
If you detect <key costume name pressed>, you should then switch to that costume!
It will switch to the costume name with the correct case even though the key pressed may have detected the other case!

*** EDIT *** CODE BELOW IS WRONG! *** I WILL FIX IT IN ANOTHER POST ***
*** IT WAS LATE WHEN I WROTE THIS ***

You can fix the code with a single additional line:

when [any v] key pressed
set [Output key v] to ()
if <key [any v] pressed?> then
switch costume to [1 v]
repeat (110)
if <key (costume [name v]::looks) pressed> then // this detects the letter whether the case matches or not
switch costume to (costume name::looks) // this switches to the letter costume of the correct case
set [Output key v] to (costume [name v]::looks)
stop [this script v]
else
next costume
end
end
end

Scratch-Minion wrote:

Scratch costume names are case sensitive, but the <key … pressed> block is not case sensitive.
If you detect <key costume name pressed>, you should then switch to that costume!
It will switch to the costume name with the correct case even though the key pressed may have detected the other case!

You can fix the code with a single additional line:

when [any v] key pressed
set [Output key v] to ()
if <key [any v] pressed?> then
switch costume to [1 v]
repeat (110)
if <key (costume [name v]::looks) pressed> then // this detects the letter whether the case matches or not
switch costume to (costume name::looks) // this switches to the letter costume of the correct case
set [Output key v] to (costume [name v]::looks)
stop [this script v]
else
next costume
end
end
end

I'll try this out!

Scratch costume names are case sensitive, but the <key … pressed> block is not case sensitive.
If you detect <key costume name pressed>, you should then switch to that costume!
It will switch to the costume name with the correct case even though the key pressed may have detected the other case!

*** Edit: I MUST HAVE HALF ASLEEP.
THE CODE BELOW ALSO DOESN'T WORK.

Create a variable Keys with the single letter names of your 110 costumes:
eg.

set [Letters v] to [abc...xyzABC...XYZ0123...]

then:

when [any v] key pressed
Get Key Pressed

define Get Key Pressed
set [Output key v] to ()
set [n v] to [1]
repeat (110)
switch costume to (join (letter (n) of (Letters)) []) // this switches to the letter costume of the correct case
if <key (costume [name v]::looks) pressed> then // this detects the letter whether the case matches or not
set [Output key v] to (costume [name v]::looks)
stop [this script v]
else
change [n v] by (1)
end
end

There is one more check that you should do!
It may be that the “any” key pressed was not a letter or character key but <Enter>, an <arrow> key etc.
If the code exits the repeat loop without having found a printable character (ie. “stop this script” will not have happened) then you should add code after the repeat loop. Note that your variable “Output key” will still be empty.

Note that the script under “when any key pressed” is inside a “run without screen refresh” custom block so it all runs immediately.
* Edit: I have added the custom block now rather than just suggesting it..

MultiTasker801 wrote:

i believe the problem is that the key pressed block is NOT case-sensitive. i'm not sure if it's actually possible to get case-sensitive inputs in scratch, barring usage of the ask block, which is obviously not ideal. there's also no method of detecting the shift key so you wouldn't be able to pick up capitals that way either.

You can detect the shift key like this.

<key [(join [] [shift]) v] pressed?>

(join [] [shift])

<key [ v] pressed?>

Another edit: I got so ninja'd.

EDawg2011 wrote:

MultiTasker801 wrote:

i believe the problem is that the key pressed block is NOT case-sensitive. i'm not sure if it's actually possible to get case-sensitive inputs in scratch, barring usage of the ask block, which is obviously not ideal. there's also no method of detecting the shift key so you wouldn't be able to pick up capitals that way either.

You can detect the shift key like this.

<key [(join [] [shift]) v] pressed?>

(join [] [shift])

<key [ v] pressed?>

Another edit: I got so ninja'd.

Actually, shifts can't even be detecting using this unless you're on Turbowarp or some other Scratch mod

Scratch-Minion wrote:

Scratch costume names are case sensitive, but the <key … pressed> block is not case sensitive.
If you detect <key costume name pressed>, you should then switch to that costume!
It will switch to the costume name with the correct case even though the key pressed may have detected the other case!

Below is my fixed fix for the code:

Create a variable Keys with the single letter names of your 110 costumes:
eg.

set [Letters v] to [abc...xyzABC...XYZ0123...]

then:

when [any v] key pressed
Get Key Pressed

define Get Key Pressed
set [Output key v] to ()
set [n v] to [1]
repeat (110)
switch costume to (join (letter (n) of (Letters)) []) // this switches to the letter costume of the correct case
if <key (costume [name v]::looks) pressed> then // this detects the letter whether the case matches or not
set [Output key v] to (costume [name v]::looks)
stop [this script v]
else
change [n v] by (1)
end
end

There is one more check that you should do!
It may be that the “any” key pressed was not a letter or character key but <Enter>, an <arrow> key etc.
If the code exits the repeat loop without having found a printable character (ie. “stop this script” will not have happened) then you should add code after the repeat loop. Note that your variable “Output key” will still be empty.

Note that the script under “when any key pressed” is inside a “run without screen refresh” custom block so it all runs immediately.
* Edit: I have added the custom block now rather than just suggesting it..

I already had it in a run without screen refresh block (but thanks for that), and I know it runs even when the key isn't a letter. I've already been adding keys such as ‘Enter’, ‘Backspace’/'Delete' and the arrow keys. Thanks for the help!

I don’t understand the solutions here since the

switch costume to [A v]
<key [(costume name) v] pressed?>

and

switch costume to [a v]
<key [(costume name) v] pressed?>

do the same thing since the key block is case insensitive. I’ve tried this in a small test case.

However, and this is an Ugly solution but you might have to borrow the old technique from a TRS-80 (model 1). The user had to enter a special character to indicate that the next letter was a capital letter.

10goto10 wrote:

I don’t understand the solutions here since the

switch costume to [A v]
<key [(costume name) v] pressed?>

and

switch costume to [a v]
<key [(costume name) v] pressed?>

do the same thing since the key block is case insensitive. I’ve tried this in a small test case.

However, and this is an Ugly solution but you might have to borrow the old technique from a TRS-80 (model 1). The user had to enter a special character to indicate that the next letter was a capital letter.

In Scratch a sprite can have 2 different costumes named A and a.
The “switch costume to …” block is case sensitive and will switch to A or a as specified.

Scratch-Minion wrote:

10goto10 wrote:

I don’t understand the solutions here since the

switch costume to [A v]
<key [(costume name) v] pressed?>

and

switch costume to [a v]
<key [(costume name) v] pressed?>

do the same thing since the key block is case insensitive. I’ve tried this in a small test case.

However, and this is an Ugly solution but you might have to borrow the old technique from a TRS-80 (model 1). The user had to enter a special character to indicate that the next letter was a capital letter.

In Scratch a sprite can have 2 different costumes named A and a.
The “switch costume to …” block is case sensitive and will switch to A or a as specified.

… but the block that actually indicates whether the button is pressed is case-insensitive so it doesn't matter what the input is and you'll always get something case-insensitive out the other end. have you considered, like, actually implementing your suggestions and seeing if they work? lol

MultiTasker801 wrote:

Scratch-Minion wrote:

10goto10 wrote:

I don’t understand the solutions here since the

switch costume to [A v]
<key [(costume name) v] pressed?>

and

switch costume to [a v]
<key [(costume name) v] pressed?>

do the same thing since the key block is case insensitive. I’ve tried this in a small test case.

However, and this is an Ugly solution but you might have to borrow the old technique from a TRS-80 (model 1). The user had to enter a special character to indicate that the next letter was a capital letter.

In Scratch a sprite can have 2 different costumes named A and a.
The “switch costume to …” block is case sensitive and will switch to A or a as specified.

… but the block that actually indicates whether the button is pressed is case-insensitive so it doesn't matter what the input is and you'll always get something case-insensitive out the other end. have you considered, like, actually implementing your suggestions and seeing if they work? lol

Yes, I have tested this.

I suggest you make a project with 2 costumes A and a.
“Switch costume to A” will always switch to costume A
“Switch costume to a” will always switch to costume a

The “key .. pressed” block is not case sensitive and the blocks below work the same, each detecting both A and a.

<key [A] pressed?>
<key [a] pressed?>

Scratch-Minion wrote:

MultiTasker801 wrote:

Scratch-Minion wrote:

10goto10 wrote:

//removed text, this thread is now getting rather long//

In Scratch a sprite can have 2 different costumes named A and a.
The “switch costume to …” block is case sensitive and will switch to A or a as specified.

… but the block that actually indicates whether the button is pressed is case-insensitive so it doesn't matter what the input is and you'll always get something case-insensitive out the other end. have you considered, like, actually implementing your suggestions and seeing if they work? lol

Yes, I have tested this.

I suggest you make a project with 2 costumes A and a.
“Switch costume to A” will always switch to costume A
“Switch costume to a” will always switch to costume a

The “key .. pressed” block is not case sensitive and the blocks below work the same, each detecting both A and a.

<key [A] pressed?>
<key [a] pressed?>

you are demonstrating great knowledge of what you're talking about, but you are not at all helping with the conversation. all you've done is say “costumes are case sensitive” while providing no solution to the question of case-sensitive input detection. it's like if you were having a conversation about which tool is best for accurate metal-working and i came along and repeatedly remarked about how copper is conductive. like that's great dude but nobody asked and nothing of value has been added to the conversation. it's particularly ridiculous because OP has already demonstrated that they are ALSO aware that costume names have unique properties. you've made up an unrelated question, answered it, and gotten defensive when it was pointed out.

OK, the issue here is the use of the keypressed method of input.

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

will both detect A or a and it doesn't matter whether you refer to a/A as hardcoded text or costume names, I don't think you can detect the difference,

If you use the ask/answer method of input you can easily detect upper or lower case but that's because we actually have the input and it's just a case of how we use it. So saying ‘if answer = a’ still doesn't distingusih between A and a but if we use tricks like the costume name being case sensitive we can distinguish between them. (This is because answer actually contains the input as typed so will contain a or A.)

I think both @Scratch-Minion and I overlooked this essential difference but apologies to @Scratch-Minion if they disagree.

Other than using the ask/answer method I can see no way to do this.

deck26 wrote:

OK, the issue here is the use of the keypressed method of input.

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

will both detect A or a and it doesn't matter whether you refer to a/A as hardcoded text or costume names, I don't think you can detect the difference,

If you use the ask/answer method of input you can easily detect upper or lower case but that's because we actually have the input and it's just a case of how we use it. So saying ‘if answer = a’ still doesn't distingusih between A and a but if we use tricks like the costume name being case sensitive we can distinguish between them. (This is because answer actually contains the input as typed so will contain a or A.)

I think both @Scratch-Minion and I overlooked this essential difference but apologies to @Scratch-Minion if they disagree.

Other than using the ask/answer method I can see no way to do this.

One thing you might be able to do for a sort of “sub shift” button is repurpose the ~ key as a shift. As using the join () () technique works with the ~ button. From there its pretty easy to differentiate shift presses.

BigSus2 wrote:

deck26 wrote:

OK, the issue here is the use of the keypressed method of input.

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

will both detect A or a and it doesn't matter whether you refer to a/A as hardcoded text or costume names, I don't think you can detect the difference,

If you use the ask/answer method of input you can easily detect upper or lower case but that's because we actually have the input and it's just a case of how we use it. So saying ‘if answer = a’ still doesn't distingusih between A and a but if we use tricks like the costume name being case sensitive we can distinguish between them. (This is because answer actually contains the input as typed so will contain a or A.)

I think both @Scratch-Minion and I overlooked this essential difference but apologies to @Scratch-Minion if they disagree.

Other than using the ask/answer method I can see no way to do this.

One thing you might be able to do for a sort of “sub shift” button is repurpose the ~ key as a shift. As using the join () () technique works with the ~ button. From there its pretty easy to differentiate shift presses.

You don't need to detect shift since you can already detect keys such as ~ or A. You just need to be able to distinguish between capital and lowercase.

MultiTasker801 wrote:

Scratch-Minion wrote:

MultiTasker801 wrote:

Scratch-Minion wrote:

10goto10 wrote:

//removed text, this thread is now getting rather long//

In Scratch a sprite can have 2 different costumes named A and a.
The “switch costume to …” block is case sensitive and will switch to A or a as specified.

-snip x2-

-explanation on keys-

<key [A] pressed?>
<key [a] pressed?>

~long quote snip~

deck26 wrote:

OK, the issue here is the use of the keypressed method of input.

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

will both detect A or a and it doesn't matter whether you refer to a/A as hardcoded text or costume names, I don't think you can detect the difference,

If you use the ask/answer method of input you can easily detect upper or lower case but that's because we actually have the input and it's just a case of how we use it. So saying ‘if answer = a’ still doesn't distingusih between A and a but if we use tricks like the costume name being case sensitive we can distinguish between them. (This is because answer actually contains the input as typed so will contain a or A.)

I think both @Scratch-Minion and I overlooked this essential difference but apologies to @Scratch-Minion if they disagree.

Other than using the ask/answer method I can see no way to do this.

They're saying that using the costume in the key pressed block you can detect case sensitive keys since the costume block is also case sensitive. If you doubt this, try testing it yourself.

PokePika__10339__ wrote:

MultiTasker801 wrote:

Scratch-Minion wrote:

MultiTasker801 wrote:

Scratch-Minion wrote:

10goto10 wrote:

//removed text, this thread is now getting rather long//

In Scratch a sprite can have 2 different costumes named A and a.
The “switch costume to …” block is case sensitive and will switch to A or a as specified.

-snip x2-

-explanation on keys-

<key [A] pressed?>
<key [a] pressed?>

~long quote snip~

deck26 wrote:

OK, the issue here is the use of the keypressed method of input.

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

will both detect A or a and it doesn't matter whether you refer to a/A as hardcoded text or costume names, I don't think you can detect the difference,

If you use the ask/answer method of input you can easily detect upper or lower case but that's because we actually have the input and it's just a case of how we use it. So saying ‘if answer = a’ still doesn't distingusih between A and a but if we use tricks like the costume name being case sensitive we can distinguish between them. (This is because answer actually contains the input as typed so will contain a or A.)

I think both @Scratch-Minion and I overlooked this essential difference but apologies to @Scratch-Minion if they disagree.

Other than using the ask/answer method I can see no way to do this.

They're saying that using the costume in the key pressed block you can detect case sensitive keys since the costume block is also case sensitive. If you doubt this, try testing it yourself.

Yeah I know, I simply misread what the other guy was saying.