No visual clues in operators for strings vs numbers vs...
See original GitHub issueObserved in the catch game playtest video:
Trying to check for the y position of the apple being below -170.
First they typed the text ‘y position’ into the first operand instead of finding the y-position reporter. They did eventually realize it didn’t match the card and found the reporter.
They typed “- 170” with a space between the -
and the 170
. This turned the value into a string, and the operator was never true. They never figured this one out.
Issue Analytics
- State:
- Created 6 years ago
- Comments:7 (5 by maintainers)
Top Results From Across the Web
Comparison Operators (Visual Basic)
Comparison operators compare two expressions and return a Boolean value that represents the relationship of their values. There are operators ...
Read more >Built-in Types — Python 3.11.1 documentation
Numbers are created by numeric literals or as the result of built-in functions and operators. Unadorned integer literals (including hex, octal and binary ......
Read more >Strings and Character Data in Python
Here's what you'll learn in this tutorial: Python provides a rich set of operators, functions, and methods for working with strings.
Read more >Conditionals and logic | Think Java | Trinket
Java has three logical operators: && , || , and ! , which respectively stand for and, or, and not. The results of...
Read more >Greater than or equal (>=) - JavaScript - MDN Web Docs
The greater than or equal (>=) operator returns true if the left operand is ... Compare bigint to number (note: bigint is not...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@heyitsmeuralex I mean that is good if they manually inputed it and not put it in like a variable…
Perhaps give the input a red border when an invalid value is given, similar to 1.4’s divide-by-zero behaviour…?
Adding a tooltip to it too (e.g. “This should be a number!”) would be a good idea, no?