Bump!

Jonathan50 wrote:

Also, why were the editable dropdowns used in the list blocks that take indices as inputs (and a few others, but I think those were all replaced with specialised inputs or ordinary dropdowns) removed? These made the list blocks easier to use and understand, and

delete (all v) of [list v]

has been replaced with a seperate block!

Not intuitive in other languages:

forigi (ĉiuj v) el [listo v]::list // deletes everything, as intended
forigi (kunligi [ĉiuj] kaj []::operators) el [listo v]::list // does nothing???
forigi (kunligi [all] kaj []::operators) el [listo v]::list // works??

Newer blocks like the translate extension work around this by accepting all translations, but this is not a perfect solution

(translate [hello] to (join [español] [])::extension) // Hola

This even works for languages not on the list, like Esperanto: (translate “Hello” to (translate “Esperanto” to “Chinese (Traditional)”))

A related issue is that booleans always return “true” and “false” in English regardless of the user's language; ideally the ST would change this, but it'd break existing projects

Sheep_maker wrote:

Newer blocks like the translate extension work around this by accepting all translations, but this is not a perfect solution

(translate [hello] to (join [español] [])::extension) // Hola

What would you expect if you place an input which doesn't appear in a dropdown in it?

A related issue is that booleans always return “true” and “false” in English regardless of the user's language; ideally the ST would change this, but it'd break existing projects

Huh. They could make it so that Booleans are localised when they appear, as in Scratch 1.4, because they're represented differently from strings, though that still doesn't help in the situation when a Boolean is casted to a string.

Bump.

Jonathan50 wrote:

Sheep_maker wrote:

Newer blocks like the translate extension work around this by accepting all translations, but this is not a perfect solution

(translate [hello] to (join [español] [])::extension) // Hola

What would you expect if you place an input which doesn't appear in a dropdown in it?

I'd expect it to do nothing and return an empty string, but upon testing it seems to fallback to English

Sheep_maker wrote:

I'd expect it to do nothing and return an empty string, but upon testing it seems to fallback to English

Okay, but there isn't something obviously right or even useful about that behavior, it's just the sort of thing Scratch users have come to expect. (I guess if error messages weren't considered deterring, then it would be good if doing such things consistently made an error message rather than doing something unexpected. But this problem is a consequence of how the language is associated with the viewer rather than the project, and the solution chosen seems innocuous enough as long as there isn't a string which means one option in one language and another in another.)

Bump.

Bump.

Bump!

Bump.

Bump.

Bump.

Bump.

Bump!

Bump.

Bump.

If your topic contains mostly bumps, it means that no one wants to discuss it anymore.

Bump.

Jonathan50 wrote:

Bump.

55.2% of this topic is bumps. Believe it or not, occasionally adding faces and exclamation points doesn't mean that you're being constructive.

1132262 wrote:

55.2% of this topic is bumps. Believe it or not, occasionally adding faces and exclamation points doesn't mean that you're being constructive.

Quite right.