I may have discovered a bug in the input function...
|
09-08-2017, 10:37 AM
Post: #1
|
|||
|
|||
I may have discovered a bug in the input function...
The type for integer in the input command is 1. Real number type is 0.
If I create an input box of type 0, I can enter 25, for example, and it'll be accepted, as will 25.5. However, if I create an input box of type 1, I cannot enter 25. I have to enter #25d to enter an integer. It SHOULD accept 25, and not accept 25.5. i.e. It should know that without the #, it's decimal. The way it's set up now, I can't stop someone from entering 2.5 (a real number with a fractional part) unless I force them to use #2d type input. The other comment I have to add, is that it's not intuitive to have the value I'm typing not appearing in real time inside the box as I'm typing. Currently it appears on the input line on the bottom of the screen, which is counterintuitive. Is there currently a way to do it properly like all other forms in the universe? i.e. The comment on the bottom acts like a mini-help, and that's fine, but the input should appear in the box itself, not at the bottom of the screen... Thanks -Donald |
|||
« Next Oldest | Next Newest »
|
Messages In This Thread |
I may have discovered a bug in the input function... - webmasterpdx - 09-08-2017 10:37 AM
RE: I may have discovered a bug in the input function... - toml_12953 - 09-08-2017, 01:15 PM
RE: I may have discovered a bug in the input function... - webmasterpdx - 09-08-2017, 04:23 PM
RE: I may have discovered a bug in the input function... - Carlos295pz - 09-09-2017, 02:56 AM
RE: I may have discovered a bug in the input function... - Joe Horn - 09-09-2017, 04:01 AM
RE: I may have discovered a bug in the input function... - Kevin Ouellet - 03-03-2022, 11:00 AM
RE: I may have discovered a bug in the input function... - parisse - 03-04-2022, 03:48 PM
|
User(s) browsing this thread: 1 Guest(s)