Discuss Scratch

Coder24
Scratcher
39 posts

Case Sensitive Equals Block

This is a pretty straight-forward suggestion. Scratch is definitely missing case sensitive functionality even though it is still possible with a lot of complicated code. This would really make things like encoders and decoders a lot more simple and comprehensive.

Thanks,
Coder24
DaSpudLord
Scratcher
1000+ posts

Case Sensitive Equals Block

I'm not going to support, but I also can't say no support…
Gaza101
Scratcher
500+ posts

Case Sensitive Equals Block

Support; how about:
<[Aa] is exactly [Aa] :: operators>

DaSpudLord wrote:

I'm not going to support, but I also can't say no support…
Then semi-support.

Last edited by Gaza101 (June 19, 2015 21:14:32)

MathlyCat
Scratcher
1000+ posts

Case Sensitive Equals Block

thelucariokid wrote:

No support, because it seems useless.
Is this a joke? Because he literally states it would make Cloud Listing easier!?

Total support for the exactly operator
DaSpudLord
Scratcher
1000+ posts

Case Sensitive Equals Block

Gaza101 wrote:

Support; how about:
<[Aa] is exactly [Aa] :: operators>
Support for this, alongside the current
<[] = []>
block.
CatsUnited
Scratcher
1000+ posts

Case Sensitive Equals Block

Support for updating the equals block or add the exactly block.
TheHockeyist
Scratcher
1000+ posts

Case Sensitive Equals Block

Pot-of-Gold wrote:

matey1234 wrote:

CatsUnited wrote:

Support for updating the equals block or add the exactly block.
This. What happens with numbers, though?
DaSpudLord
Scratcher
1000+ posts

Case Sensitive Equals Block

TheHockeyist wrote:

Pot-of-Gold wrote:

matey1234 wrote:

CatsUnited wrote:

Support for updating the equals block or add the exactly block.
This. What happens with numbers, though?
Hm. I think that exact, number-for-number copies should be true, but stuff like <01 is exactly 1> would be false.

Last edited by DaSpudLord (June 20, 2015 03:34:17)

scrooge200
Scratcher
1000+ posts

Case Sensitive Equals Block

We already have an “equals” block, so adding a new one would if useless. I also don't understand, are you asking for something like this?
<caps lock on?::sensing>
DaSpudLord
Scratcher
1000+ posts

Case Sensitive Equals Block

scrooge200 wrote:

We already have an “equals” block, so adding a new one would if useless. I also don't understand, are you asking for something like this?
<caps lock on?::sensing>
That's not at all what we're suggesting. Here, I'll explain. You know how the current equals block isn't case sensitive? For example…
<[A] = [a]> //This reports as true, even though the letters are different cases.

<[Goodbye] = [goodBye]>//This also reports as true.
We're suggesting a block like the equals block, except it would be case sensitive-
<[A] is exactly [a]::operators>//Would report as false because the case doesn't match.

<[Goodbye] is exactly [goodBye]::operators>//Would also report as false.

<[Goodbye] is exactly [Goodbye]::operators>//Would report as true because the case matches.

Last edited by DaSpudLord (June 20, 2015 05:27:37)

stickfiregames
Scratcher
1000+ posts

Case Sensitive Equals Block

Support to add a new block, no support to update the existing one because it would break existing projects.
ElectroElectro2004
Scratcher
100+ posts

Case Sensitive Equals Block

Semi-support. It could be workarounded, like you said, but can also help. How about next to each string, a switch for case sensitive?
19f8361
Scratcher
500+ posts

Case Sensitive Equals Block

ElectroElectro2004 wrote:

Semi-support. It could be workarounded, like you said, but can also help. How about next to each string, a switch for case sensitive?

umm… there is no workaround, i support.
IronBit_Studios
Scratcher
1000+ posts

Case Sensitive Equals Block

Support.
ev3coolexit987654
Scratcher
1000+ posts

Case Sensitive Equals Block

Support.
DaSpudLord
Scratcher
1000+ posts

Case Sensitive Equals Block

19f8361 wrote:

ElectroElectro2004 wrote:

Semi-support. It could be workarounded, like you said, but can also help. How about next to each string, a switch for case sensitive?

umm… there is no workaround, i support.
Actually there is, but it's kinda complicated. Try searching for it.
Nether_before
Scratcher
1000+ posts

Case Sensitive Equals Block

Support!
Voltalent
Scratcher
1 post

Case Sensitive Equals Block

Support!

I ran into this while building a game which will help my students learn to type passwords correctly…





Pezd
Scratcher
100+ posts

Case Sensitive Equals Block

I support the
<[] is exactely []:: operators>
block. Although I definitely do not support the updating of the
<[] = []>
block. Mabye a block like this could work.
<letter () of [] is [ v]:: operators>
And the pulldown contains ‘uppercase’ and ‘lowercase.’
miniepicness
Scratcher
1000+ posts

Case Sensitive Equals Block

I support the exactly, nowhere near supporting updating the equals though

Powered by DjangoBB