Case Sensitive Equals Block

56-s

-Trufful- wrote:
Kind of weird that scratch doesn't have this
I support! :3

No it is not weird it is normal and it is too complicated for kids to understand.

ajskateboarder

56-s wrote:
-Trufful- wrote:
Kind of weird that scratch doesn't have this
I support! :3
No it is not weird it is normal and it is too complicated for kids to understand.

Uhhh no not really

That's like saying 1.1 equals 1 because 1.1, when rounded down, is also 1. Most kids probably don't want this kind of forced behavior

EDawg2011

bump
“Sorry, you have to wait 60 seconds between posts.”

Malicondi

bump, I don't know why this isn't already a thing as since the blocks run using JS, and JS is case sensitive with “==”, I don't understand why this doesn't already work.

starlightsparker

How about

case sensitive {
if <(answer) = [AbC]> then
say [the answer was AbC! Your correct!]
end
}:: sensing cap

among_us1w2

starlightsparker wrote:

How about

case sensitive {
if <(answer) = [AbC]> then
say [the answer was AbC! Your correct!]
end
}:: sensing cap

why would it be a c block? what if i put move 10 steps?

starlightsparker

among_us1w2 wrote:
starlightsparker wrote:
How about
case sensitive {
if <(answer) = [AbC]> then
say [the answer was AbC! Your correct!]
end
}:: sensing cap
why would it be a c block? what if i put move 10 steps?

then it wouldn’t work-

But it could be like

<case sensitive <(answer)=[AbC]>::sensing

Last edited by starlightsparker (March 19, 2024 19:49:33)

marsmark

add this in 4.0.

8to16

marsmark wrote:
(#88)
add this in 4.0.

please explain why you support

Scyth3d

I believe we should have a

Case sensitive <>::sensing boolean

But i DO NOT support updating the

<[] = []>

block. It not being case sensitive makes my life a lot easier

Last edited by Scyth3d (May 3, 2025 16:07:32)

undeterministic3

Malicondi wrote:
bump, I don't know why this isn't already a thing as since the blocks run using JS, and JS is case sensitive with “==”, I don't understand why this doesn't already work.

equality uses this function in scratch: https://github.com/scratchfoundation/scratch-vm/blob/develop/src/util/cast.js#L121

Scyth3d wrote:
I believe we should have a
Case sensitive <>::sensing boolean
But i DO NOT support updating the
<[] = []>
block. It not being case sensitive makes my life a lot easier

How would this new block work?

masonhugokingcraft

Support, as well as adding these

<[apple] contains [A]? case sensitive>
(item # of [thing] in [list v] case sensitive)

undeterministic3

masonhugokingcraft wrote:
Support, as well as adding these
<[apple] contains [A]? case sensitive>
(item # of [thing] in [list v] case sensitive)

No.

Instead we should make one global case sensitive thing. The reason for this is that if somebody wants to create a simple switch that would change all the code they wouldn't want to change blocks. Maybe a target dependent check. But besides equality is all checked in one place: https://github.com/scratchfoundation/scratch-vm/blob/develop/src/util/cast.js#L121 so we should add a parameter. The commit that would be made could be https://github.com/PlayfulMathematician/scratch-vm/commit/64f53ce234220d8396f05e0cc337d827e245c49d and then we could modify the other blocks to account for this new change

Scyth3d

undeterministic3 wrote:
How would this new block work?

Any Boolean put inside the new block would be case sensitive

Case sensitive <[a] = [A]>::sensing boolean

Would return false

Last edited by Scyth3d (May 23, 2025 15:36:15)

The_Blue_J

DaSpudLord wrote:
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.

Ain't that hard, if you know that costumes are case sensitive

medians

The_Blue_J wrote:
DaSpudLord wrote:
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.
Ain't that hard, if you know that costumes are case sensitive

People might not be aware of that, and adding every costume is tedious, and is pretty annoying to do, when you could instead use a single block. Also, you may have to loop through every character in a string. However, you can backpack this:
https://scratch.mit.edu/projects/10213040/

Last edited by medians (May 24, 2025 13:23:02)

tagrim123

56-s wrote:
-Trufful- wrote:
Kind of weird that scratch doesn't have this
I support! :3
No it is not weird it is normal and it is too complicated for kids to understand.

Hard to understand? I thought

[foo] is exactly [bar] ::boolean operators

was pretty straight-foward.

medians

Bringing this topic up (someone thought that the block being case-insensitive was a bug)

Lepus-Lacarotte

Support. I also had the problem with a quiz program, that's why I support.
LL

CodeComet6161

bump

Discuss Scratch