1 sentence description of the problem (I was doing _________, and then __________ happened): I noticed I can pull up the keyboard while inputting a number into a set position block and decided to mess with it because why not.
Steps that the Hopscotch team can take to reproduce my problem every time:
Tap a bubble in the Set Position block
Switch to keyboard using the Aa button
Input text potentially including but not solely comprised of numbers, play project
Object is set to position (0, 0) — the text coordinates don’t do anything
I expected this to happen:
I was pretty sure it was a bug, and expected inputting the “coordinates” (-1 is, superior) to not work.
But instead this happened:
It did what I expected — nothing. (I mean, where are the coordinate (-1 is, superior) on the screen?) But I figure it shouldn’t be possible to be able to input text coordinates like this.
The black clone — the one with the text coordinates — is the same size as the other squares on the screen. Only one quarter of it is shown because the center of it is at the coordinates (0, 0).
I assume Set Position isn’t the only block you can input text into when the block only does anything if you input numbers, but I haven’t checked.
This part of the new update. I’m pretty sure it’s not for the movement block. And unless you set the text to something then it would always equal 0.
It is resulting in one issue where the keyboard will automatically switch to text when you open an empty parameter, even where it’s a block that takes numeric input (e.g. Move Forward, Turn) and strings don’t do anything when the project is played.
This was unintentional but had been around for a while, since string/text operators were introduced.
Only parameters for the + operator, and parameters for custom abilities/custom rules, will show Aa button. And only they will open up the text keyboard when empty.
The other numeric parameters will show the numbers keyboard when empty. And they won’t show the Aa button when the numbers keyboard is up.
@Yuanyuan@t1_hopscotch ^^^ I think you forgot about the multi-purpose parameters (ones that should allow both numbers and text). The parameters in the equality operators seem to think it can only support numbers and variables…
(Bobinny, as a workaround, you can just copy some text and paste it into the parameter).
After doing some testing, it seems to just be the equality operators that have this issue.
(=, ≠, >, <, >=, <=)
Also, for some reason you can copy and paste text into places where it shouldn’t
(not, and, or (logical operators), a blank if statement itself, and pretty much every block where it doesn’t support text)
Oh right I had forgotten about equality operators. Thanks for letting me know — we will need to fix that. It may be some time before that change comes out though.
