Post by: SMcNeill on December 04, 2019, 10:58:01 am
The answer has always been the same: "It doesn't. You'll just have to write your own input handler to do that!"
So, after ages of telling people they had to write their own, I finally needed to write my own input handler, so I thought I'd share:
Code: [Select]
_CONTROLCHR OFF
PRINT ExtendedInput$
FUNCTION ExtendedInput$
PCOPY 0, 1
A = _AUTODISPLAY: X = POS(0): Y = CSRLIN
_KEYCLEAR
DO
PCOPY 1, 0
IF _KEYDOWN(100307) OR _KEYDOWN(100308) THEN AltDown = -1 ELSE AltDown = 0
k = _KEYHIT
IF AltDown THEN
SELECT CASE k 'ignore all keypresses except ALT-number presses
CASE 48 TO 57: AltWasDown = -1: alt$ = alt$ + CHR$(k)
END SELECT
ELSE
SELECT CASE k 'without alt, add any keypresses to our input
CASE 8: oldin$ = in$: in$ = LEFT$(in$, LEN(in$) - 1) 'backspace to erase input
CASE 9: oldin$ = in$: in$ = in$ + SPACE$(4) 'four spaces for any TAB entered
CASE 32 TO 128
IF _KEYDOWN(100305) OR _KEYDOWN(100306) THEN
IF k = 118 OR k = 86 THEN oldin$ = in$: in$ = in$ + _CLIPBOARD$ 'ctrl-v paste
IF k = 122 OR k = 90 THEN SWAP in$, oldin$ 'ctrl-z undo
ELSE
oldin$ = in$: in$ = in$ + CHR$(k) 'add input to our string
END IF
END SELECT
END IF
alt$ = RIGHT$(alt$, 3)
IF AltWasDown = -1 AND AltDown = 0 THEN
v = VAL(alt$)
IF v >= 0 AND v <= 255 THEN in$ = in$ + CHR$(v)
alt$ = "": AltWasDown = 0
END IF
blink = (blink + 1) MOD 30
LOCATE Y, X: IF blink \ 15 THEN PRINT in$ ELSE PRINT in$ + "_"
_DISPLAY
_LIMIT 30
LOOP UNTIL k = 13
PCOPY 1, 0
LOCATE Y, X: PRINT in$
ExtendedInput$ = in$
IF A THEN _AUTODISPLAY
END FUNCTIONThis is used as basically a replacement for INPUT$, and handles quite a few special cases for us.
- We handle regular input, as normal.
- CTRL-V works as a paste command, so we can paste clipboard text into the input.
- CTRL-Z works as an undo, to undo the last change to our text.
- ALT-number keys can be used to enter an ASCII character into the input.
- TAB inserts four spaces into our input automatically for ease of formatting.
Like INPUT, this pauses program execution until we finish our input, and it plays nicely with background processes.
Try it out and play around with it. See if it performs as you'd expect/want it to. Type some junk in it. Then hold down ALT and type in a few numeric codes. (ALT-65 is "A", ALT-1 is the little smiley face, for example.) Try CTRL-V to paste something, and CTRL-Z to undo your last input (which can be quite useful if you paste the wrong junk into your text with CTRL-V).
I think this should be easily expandable so people could customize it to suit their own specific needs, if they have any which is different from what it's currently doing. At the moment, it's doing all that I'd expect it to do, for me, and I hope others might find it useful as well.
At least now, when somebody asks about "Why can't INPUT do XXXX" again in the future, I can at least say, "Take a look at this, see if it suits your needs, and if not, maybe it'll be a nice starting point to help you write your own input handler." :D
Post by: bplus on December 04, 2019, 11:04:35 am
Post by: SMcNeill on December 04, 2019, 11:12:36 am
Post by: bplus on December 04, 2019, 11:18:29 am
Post by: SMcNeill on December 04, 2019, 11:24:19 am
Hey Steve is it possible to do multiple lines, CHR$(10) Line Feed? That would be really cool!
Wouldn't you just take out the first line so that _CONTROLCHR was ON instead of OFF, and then type in input with ALT-10.
Say an INPUT of "As" + ALT-10 + "the world turns"...
The above should display as :
"As"
"the world turns"
(And that CHR$(10) is preserved in there for formatting.)
Post by: Pete on December 04, 2019, 11:34:48 am
Pete :D
You know you can't please everyone, so you have to please myself...
Post by: Cobalt on December 14, 2019, 11:09:41 pm
As usual, nice work Steve.
Post by: SMcNeill on December 15, 2019, 02:54:31 pm
Code: QB64: [Select]
- PRINT ExtendedInput$
- FUNCTION ExtendedInput$
- CP = 0: OldCP = 0 'Cursor Position
- k = _KEYHIT
- CASE 8
- oldin$ = in$
- CASE 9
- oldin$ = in$
- OldCP = CP
- CP = CP + 4
- oldin$ = in$
- 'CTRL-V leaves cursor in position before the paste, without moving it after.
- 'Feel free to modify that behavior here, if you want it to move to after the paste.
- oldin$ = in$
- OldCP = CP
- CP = CP + 1
- CP = 0
- oldin$ = in$
- CP = CP - 1
- CP = CP + 1
- alt$ = "": AltWasDown = 0
- LOCATE Y, X
- _LIMIT 30
- ExtendedInput$ = in$
Added on to the basic functionality presented in the original post so that now:
- arrow keys move the cursor position inside the text.
- Home moves the cursor to the beginning of the text.
- End moves the cursor to the end of the text.
- Delete now deletes a text character to the right of the cursor.
These basic capabilities make going back and editing our text much simpler and efficient than just hitting backspace until we find our glitch and then retype everything over from that point forward.
And the reason I didn't just replace the original post with this one is simply in case someone wants to write their own extended input handler. Often, it's best to keep the base process as simple as possible, if others are going to build upon it later, rather than overly complicate things which makes it harder for them to sort out what's going on and alter/add to the original. So, I figure in this case, simply posting both versions is the simplest way to go -- a basic routine which folks can enhance themselves to suit their personal needs, and a more robust version which offers a few more bells and whistles for plug-n-play usability.
Post by: STxAxTIC on December 16, 2019, 10:04:43 pm
So I was thinking (over the years but) recently (due to this post) that a different (and in some cases, better) extended input would not hang up the whole program with a DO... LOOP right in the function, but instead run on a timer to capture input and keep track of a cursor in exactly the way you make it appear, but let other things run while this is happening.
Case in point: my "universal" Sprezzo program, in client mode, can also log into chat rooms. Problem is, in order to watch the chat happen, an INPUT-like statement can't be open. Having something that passively log the keystrokes is a lot better. The old Sprezzo in fact did this, but the function wasn't just a plug-n'-play black box like you're going for.
Short story long, do you find it worth making a passive extended input function? Cause I might, but don't wanna steal your thunder. BUT... since you're kindof setting a standard with this one, there's no reason not to have a second one look and feel the same.
Post by: SMcNeill on December 16, 2019, 10:34:30 pm
Heya Steve,
So I was thinking (over the years but) recently (due to this post) that a different (and in some cases, better) extended input would not hang up the whole program with a DO... LOOP right in the function, but instead run on a timer to capture input and keep track of a cursor in exactly the way you make it appear, but let other things run while this is happening.
Case in point: my "universal" Sprezzo program, in client mode, can also log into chat rooms. Problem is, in order to watch the chat happen, an INPUT-like statement can't be open. Having something that passively log the keystrokes is a lot better. The old Sprezzo in fact did this, but the function wasn't just a plug-n'-play black box like you're going for.
Short story long, do you find it worth making a passive extended input function? Cause I might, but don't wanna steal your thunder. BUT... since you're kindof setting a standard with this one, there's no reason not to have a second one look and feel the same.
Terry Ritchie’s GLInput Library is passive as you’re describing it. Your program can run in the background, with it capturing input for you. I’ve used it several times in the past, and it’s extremely powerful and flexible once you sort out how to use it. What I’ve got here is mainly just a simple substitute for INPUT, and it’s intended to pause program execution until ENTER is hit (just as INPUT does).
If you need passive input, check out Terry’s library before you go about building your own. Even if it’s not what you needed, it’s well commented and documented, and might help you on the path of crafting your own easier. ;)
Post by: STxAxTIC on December 16, 2019, 10:43:00 pm
Quote
Terry Ritchie’s GLInput Library is passive as you’re describing it. Your program can run in the background, with it capturing input for you. I’ve used it several times in the past, and it’s extremely powerful and flexible once you sort out how to use it. What I’ve got here is mainly just a simple substitute for INPUT, and it’s intended to pause program execution until ENTER is hit (just as INPUT does).
If you need passive input, check out Terry’s library before you go about building your own. Even if it’s not what you needed, it’s well commented and documented, and might help you on the path of crafting your own easier. ;)
Say, good to know. My ego pretty much doesn't allow me to use someone else's code, but I *may* give it a look. Tee hee hee.
Post by: bplus on December 16, 2019, 10:44:41 pm
Post by: STxAxTIC on December 16, 2019, 11:36:22 pm
Post by: SMcNeill on February 02, 2021, 01:15:51 am
Code: QB64: [Select]
- OEInput "{P}Enter a password =>", a$
- PRINT a$
- OEInput "{UI}Enter an unsigned integer =>", a$
- PRINT a$
- OEInput "{I}Enter an integer=>", a$
- PRINT a$
- OEInput "{F}Enter a float=>", a$
- PRINT a$
- OEInput "{IL10}Enter an integer of less than 10 digits =>", a$
- PRINT a$
- OEInput "{X15,Y15}Enter whatever at loc 15,15 =>", a$
- PRINT a$
- OEInput "{D}Check to make certain paste is disabled here =>", a$
- PRINT a$
- CP = 0: OldCP = 0 'Cursor Position
- j = j + 1
- j = j + 1
- j = j + 1
- k = _KEYHIT
- CASE 8
- oldin$ = in$
- CASE 9
- oldin$ = in$
- OldCP = CP
- CP = CP + 4
- oldin$ = in$
- 'CTRL-V leaves cursor in position before the paste, without moving it after.
- 'Feel free to modify that behavior here, if you want it to move to after the paste.
- check_input:
- oldin$ = in$
- good_input:
- OldCP = CP
- CP = CP + 1
- CP = 0
- oldin$ = in$
- CP = CP - 1
- CP = CP + 1
- k = v
- alt$ = "": AltWasDown = 0
- GOTO check_input
- LOCATE Y, X
- PRINT prompt$;
- _LIMIT 30
- LOCATE Y, X:
- PRINT prompt$; in$
- result$ = in$
It does all it did before, but now you can send it a prompt to print to the screen, much like INPUT "Enter a number => "; n$
And, since I'm adding a prompt, I'm adding it's own little control system of limiters which we play around with for our text.
Control starts as the first digits of your prompt and begin with an "{" and end with an "}", and we add our control codes inside those braces.
We can limit by number (integer, unsigned, or float). We can limit by length. We can position our prompt without using locate. We can hide user input for passwords. We can disable paste capabilities (which probably don't make sense to have, if we're going to limit input with other things...) Alt-### can be used to enter ASCII characters via the num pad now.
We can do one of these things, or all of these things, or none of these things!
And, if folks need something else added to this, feel free to speak up while I'm still at home and have a few days where I don't have to take care of mom. (Which gives you the next 3 days, or so, to make requests for additions/alterations.)
My philosophy is, "If you're going to over engineer something, then by God, do it right!"
Post by: STxAxTIC on February 02, 2021, 01:21:20 am
Quote
My philosophy is, "If you're going to over engineer something, then by God, do it right!"
Ahem, where's OPTION _EXPLICIT?
Post by: STxAxTIC on February 02, 2021, 01:27:34 am
In "enter a float"... type something with a decimal, and then backspace through the decimal... you can never type a decimal again after that
Post by: SMcNeill on February 02, 2021, 01:33:56 am
Ahem, where's OPTION _EXPLICIT?I dunno. In somebody else’s code?? Personally, I never use it. It defeats the purpose of having BASIC allocate and define your variables on the fly for you. :P
Feel free to add it if you need it. I usually don’t get around to stuff like that until I’m completely finished tinkering with the code.
I’m thinking for floats to have them in a F12.2 format. The example there would allow up to 12 digits before the decimal, 2 after.
I'll also add a command to move cursor to after a paste.
Maybe even add an option to auto-comma values...
So still some more tweaking to go here.
Post by: SMcNeill on February 02, 2021, 01:34:37 am
Aright here's a bug for ya.
In "enter a float"... type something with a decimal, and then backspace through the decimal... you can never type a decimal again after that
Good catch. I'll address that tomorrow as well. ;)
Post by: STxAxTIC on February 02, 2021, 01:40:27 am
[ This attachment cannot be displayed inline in 'Print Page' view ]
Post by: SMcNeill on February 02, 2021, 10:41:17 am
Code: QB64: [Select]
- OEInput "{F-.2}Enter a float (Unlimited.2)=>", a$
- PRINT a$
- OEInput "{F0.2}Enter a float (0.2) =>", a$
- PRINT a$
- OEInput "{F9.2}Enter a float (9.2) =>", a$
- PRINT a$
- OEInput "{F9.-}Enter a float (9.unlimited) =>", a$
- PRINT a$
- OEInput "{P}Enter a password =>", a$
- PRINT a$
- OEInput "{UI}Enter an unsigned integer =>", a$
- PRINT a$
- OEInput "{I}Enter an integer=>", a$
- PRINT a$
- OEInput "{IL10}Enter an integer of less than 10 digits =>", a$
- PRINT a$
- OEInput "{X15,Y15}Enter whatever at loc 15,15 =>", a$
- PRINT a$
- OEInput "{D}Check to make certain paste is disabled here =>", a$
- PRINT a$
- OEInput "Enter whatever here, but use paste. See if the cursor remains BEFORE the paste. => ", a$
- PRINT a$
- OEInput "{V}Enter whatever here, but use paste. See if the cursor moves AFTER the paste. => ", a$
- PRINT a$
- PRINT "Press <ANY KEY> to clear the screen -- we're getting full!"
- OEInput "{H}This should hide itself, after you enter whatever =>", a$
- PRINT "Is the question and input gone? This line should be at the top left corner of your screen."
- PRINT "And here's your input => "; a$
- 'limit VALUES:
- '1 = Unsigned
- '2 = Integer
- '4 = Float
- '8 = Who cares. It's handled via internal variables and we don't need to know a type for it.
- OX = X: OY = Y 'original x and y positions
- CP = 0: OldCP = 0 'Cursor Position
- length_limit = -1 'unlimited length input, by default
- float_before_limit = GetValue(limiter$, "F")
- length_limit = GetValue(limiter$, "L")
- X = GetValue(limiter$, "X")
- Y = GetValue(limiter$, "Y")
- k = _KEYHIT
- CASE 8
- oldin$ = in$
- CASE 9
- oldin$ = in$
- OldCP = CP
- CP = CP + 4
- oldin$ = in$
- temp$ = _CLIPBOARD$
- 'CTRL-V leaves cursor in position before the paste, without moving it after.
- 'Feel free to modify that behavior here, if you want it to move to after the paste.
- check_input:
- oldin$ = in$
- OldCP = CP
- CP = CP + 1
- OldCP = CP
- CP = CP + 1
- good_input:
- OldCP = CP
- CP = CP + 1
- CP = 0
- oldin$ = in$
- CP = CP - 1
- CP = CP + 1
- k = v
- alt$ = "": AltWasDown = 0
- GOTO check_input
- LOCATE Y, X
- PRINT prompt$;
- _LIMIT 30
- LOCATE OY, OX
- LOCATE Y, X
- PRINT prompt$; in$
- result$ = in$
- GetValue = -1 'unlimited
- j = j + 1
Personally, I think even what we have here so far, is a pretty neat little bit of input handling for us. Being able to limit input by types (integer, unsigned, float, or string), is a pretty nice little option for any input routine, as it helps prevent errors from the user-entry level -- and that can stop a whole lot of error checking from ever being necessary. After all, if I *KNOW* that all an user can input is values from 0 to 9 for a numeric input, then I don't have to error-check later for dollar signs, commas, or stray sneeze input.
We can now limit floats by a before the decimal and after the decimal syntax. We have an option to move our cursor to after a paste (default has it staying before). We have an option to turn our text into a pop-up style input, where it completely disappears off the screen once we're done with it.
I guess all the basic legwork is done now. Now, I guess next, I'll work up an {A} option to create an ASCII-Box similar to the one STx presented above. Unless someone comes across a glitch somewhere for me to sort out?
(Which wouldn't surprise me one bit. After all, OEInput is starting to become a rather complex little set of work here! The more complex something gets, the more likely it is to have unexpected glitches pop-up in things!)
Post by: FellippeHeitor on February 02, 2021, 11:57:17 am
While the hood is open, maybe it's worth dressing up the whole thing in an ascii-box too? Then it'll be an alternative to this box used in several projects around here:
🎶🎵 Don't go ditching my box
I know it's not so alright
Oh honey if it gets used then
there is something of good... pam pam, pam pam, pam 🎶🎵
Post by: STxAxTIC on February 02, 2021, 02:47:58 pm
But I don't want Steve to fall into the same trap. Now there's a milestone to *pass*, not just drive under.