forkmanb wrote:

support… though wouldn't it be easier to not make a separate block and just make it an option of the “___ of” block?

[unicode v] of (put this here) :: operators

idk.. maybe someone has put this out there in the 10 pages this suggestion has.

(edited to make it clearer)

forkmanb wrote:

support… though wouldn't it be easier to not make a separate block and just make it an option of the “___ of” block?

([unicode v] of (put this here))::green

idk.. maybe someone has put this out there in the 10 pages this suggestion has.

I suppose this may be included somewhere.

To my knowledge, I think currently the only block that returns a number from a text (string) is the (length of) that can be grouped together with.

However, some minor difference is that unicode (or something like case-sensing) blocks should typically take only 1 character no matter how many characters are received. This contradicts the length block, which is supposed to accept input of arbitrary length.

This may also raise an unsolved issue about whether the code of the first character, -1, false, or other output (e.g. all codepoints concatenated by space character) to be returned if the input to some (get code of) block is empty, or contains more than 1 characters.

Here’s something

What if the provided string has move than 1 character in it

cookieclickerer33 wrote:

(#203)
Here’s something

What if the provided string has move than 1 character in it

It could only check for the first one, or return a list of codepoints.

support would make cloud variables waaaaaaaaay easier

KingRat_1 wrote:

support would make cloud variables waaaaaaaaay easier

I know, but that would also make it easier to make chatroons on Scratch.

mumu245 wrote:

cookieclickerer33 wrote:

(#203)
Here’s something

What if the provided string has move than 1 character in it

It could only check for the first one, or return a list of codepoints.

How would that work?

Support.
We would have more need to look for the character on the web.

Not Unicode but ASCII…anyway, use as a case detector is certainly interesting.
Support.

wilhelm43 wrote:

(#209)
Not Unicode but ASCII

It should support Unicode: ASCII is a subset of unicode.

I SUPPORT this thread so much

Support, the workarounds take up lots of project data space and it could be dumbed down to “character with number ()” and "number of character []". New users would likely quickly find that each character had a different number.