donotforgetmycode

The block
<color [#b82cc1] is touching [#374fb3] ?>
is very unintuitive. When I started Scratch I thought it returned true whenever the first colour is touching the second colour, because that's what the name implies. It actually only returns true if the sprite is touching the second colour. Please change it to this:
<color [#b82cc1] on this costume is touching [#374fb3] ? ::sensing>

Pianostar4

Support, actually, until now I thought it was that way too, and I've been a user for 3 years!

donotforgetmycode

bump

donotforgetmycode

bump

donotforgetmycode

pmub

han614698

No support. I don’t understand why it has to be this way… why can’t it be anywhere in the screen?

mumu245

han614698 wrote:

No support. I don’t understand why it has to be this way… why can’t it be anywhere in the screen?
Well this would break most projects.

Thingied

han614698 wrote:

why can’t it be anywhere in the screen?
Probably because it's supposed to be a variation of the normal touching color block.

ScolderCreations

No support, the new name looks long and confusing.

donotforgetmycode

ScolderCreations wrote:

No support, the new name looks long and confusing.
What about this:
<touching color [#b82cc1] with [#374fb3] ? ::sensing>

ScolderCreations

donotforgetmycode wrote:

ScolderCreations wrote:

No support, the new name looks long and confusing.
What about this:
<touching color [#b82cc1] with [#374fb3] ? ::sensing>
super confusing. Maybe
<color [#df879c] is touching [#0d495f] ?>
should remain as it is.

donotforgetmycode

Honestly I think the block should be removed, I've literally never seen it used in a project before

ScolderCreations

If the block was removed, we'd just have to add it back, as the workaround is nearly impossible.

donotforgetmycode

ScolderCreations wrote:

If the block was removed, we'd just have to add it back, as the workaround is nearly impossible.
Maybe it should be hidden block like
for [i v] in (10) {
} :: control
and
when this sprite touches [sprite1 v] :: events hat

ScolderCreations

Those blocks are hidden, because they have more simple workarounds. And, they only existed in an experimental version, while this block has been around for quite a while.

Quantum-Cat

No Support. Scratch puts similar blocks together (for example, the say blocks are separated from the costume and backdrop blocks by a space) and since the other 3 blocks with the <color () is touching () ?> are all related to the surroundings of the sprite they are used in, it would make since that it would also behave in the same way.


donotforgetmycode

Quantum-Cat wrote:

No Support. Scratch puts similar blocks together (for example, the say blocks are separated from the costume and backdrop blocks by a space) and since the other 3 blocks with the <color () is touching () ?> are all related to the surroundings of the sprite they are used in, it would make since that it would also behave in the same way.
snip
I'm not asking for the block to behave differently, I'm asking it to be renamed
Sorry, you have to wait 60 seconds between posts.

Quantum-Cat

donotforgetmycode wrote:

Quantum-Cat wrote:

No Support. Scratch puts similar blocks together (for example, the say blocks are separated from the costume and backdrop blocks by a space) and since the other 3 blocks with the <color () is touching () ?> are all related to the surroundings of the sprite they are used in, it would make since that it would also behave in the same way.
snip
I'm not asking for the block to behave differently, I'm asking it to be renamed

What I meant by this is that a person will probably expect it to behave the same as the others, so there is no need to rename it.

donotforgetmycode

Quantum-Cat wrote:

What I meant by this is that a person will probably expect it to behave the same as the others, so there is no need to rename it.
But when I joined Scratch I didn't expect it to behave the same

ScolderCreations

donotforgetmycode wrote:

Quantum-Cat wrote:

What I meant by this is that a person will probably expect it to behave the same as the others, so there is no need to rename it.
But when I joined Scratch I didn't expect it to behave the same
that's just you though.