09-10-2024, 08:43 PM
Exactly. The built-in InputBox sometimes hides behind the program screen and there are other reasons why I wrote my own version. What is interesting is that the _MessageBox never hides behind the program window (with the correct combination of _AutoDisplay and _Display), but this approach did not help me with the _InputBox.
Instead of criticizing it, I simply wrote my own solution.
Well, it will require writing one more extensive function. This is what I plan to do in the foreseeable future, and the MessageBox should properly consist of it.
The output of the function on the screen will be... a cursor. Yeah. It will be let's say 500-700 lines of code and the output will be a flashing cursor!
I'm not kidding. Imagine why: You draw dialog boxes with the LINE command, it goes fast. Now imagine a form with text. There will be (on that form) for example a field: Name, another field: surname, another field with address and so on. With the what do I want to write function, you just enter the starting position, the number of characters, maybe the font style - and in fact, most of what you need for this already contains a description of the behavior of the cursor in this program, you just need to pull it out and adapt it. Input does not respond to the mouse and such a thing is missing here. Come to think of it, actually Input can't even be (directly) placed on the screen outside of text commands with the Locate command, isn't there something like InputString (derived from PrintString) in graphics coordinates? Sure, one could manipulate the graphic output of the Input command via PutImage.... but since it's already so well described, tomorrow I'll try to write something along the lines of what I'm describing here.
Instead of criticizing it, I simply wrote my own solution.
Well, it will require writing one more extensive function. This is what I plan to do in the foreseeable future, and the MessageBox should properly consist of it.
The output of the function on the screen will be... a cursor. Yeah. It will be let's say 500-700 lines of code and the output will be a flashing cursor!
I'm not kidding. Imagine why: You draw dialog boxes with the LINE command, it goes fast. Now imagine a form with text. There will be (on that form) for example a field: Name, another field: surname, another field with address and so on. With the what do I want to write function, you just enter the starting position, the number of characters, maybe the font style - and in fact, most of what you need for this already contains a description of the behavior of the cursor in this program, you just need to pull it out and adapt it. Input does not respond to the mouse and such a thing is missing here. Come to think of it, actually Input can't even be (directly) placed on the screen outside of text commands with the Locate command, isn't there something like InputString (derived from PrintString) in graphics coordinates? Sure, one could manipulate the graphic output of the Input command via PutImage.... but since it's already so well described, tomorrow I'll try to write something along the lines of what I'm describing here.