i have no idea which category to put this post in.
making a custom block with a dropdown with an option any=$_any will turn $_any to $_random.
i have no idea why this is the case.
Is it hindering a block you are trying to build? I can't think of any (^_^) use cases for any=$_any. Just do any or $_any I guess...
To me, Help with Snap! > Snap! Editor or Bug reports > Snap! Bugs (if you think that is a bug) fit more. You aren't suggesting anything to be changed in the post.
yes. i’m working on a library working with a new datatype ‘pattern’ that acts similar to a javascript regular expression. one of these blocks would be (pattern {
character[any v]::#bb2ead}::#bb2ead
the block ‘character’ appends one letter character to the ‘pattern’. the ‘any’ dropdown has one option: the ‘any’ selector, to select ‘any’ character. selecting ‘any’ gives ‘random’ instead, making it seem like the character is random, which is confusing. a random unicode character? latin character? it’s confusing for people using the library, which i AM planning to publish.
I think this is because the list blocks used to have “any” instead of “random”
that’s intentional. There’s even an English translation that does that. We’re using the “any” string for random list items etc. At first - when I was co-developing the list feature for Scratch - we named it “any”. Then all the Berkeley folks started to freak out because they had HoFs in mind, so we renamed it to “random”. Then, of course, Scratch took out the “random item” feature altogether, and now it’s only in Snap.
Strings that already have a translation - including a.n “English” one - can only be used in that way. But you can invent your own, e.g. you could use something like “arbitrary”, or “any letter” in your block’s dropdown menu.