Timeline for Cross platform raw input handling in C/C++ for Linux and Windows
Current License: CC BY-SA 4.0
13 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 15 at 10:01 | answer | added | FLAK-ZOSO | timeline score: 0 | |
| Dec 9, 2024 at 9:20 | comment | added | user272752 | @FLAK-ZOSO "that import can be redundant" C source code (and a coder) does not "import" anything. C is not python or java. Please carefully re-read the early chapters of almost any textbook. There are some basic concepts you really want to have mastered in order to make progress with C or C++... | |
| Dec 9, 2024 at 9:15 | comment | added | user272752 | @FLAK-ZOSO My pedantry was not called for. I apologise... The "jargon-y" word I'd suggest you use going forward is "echo"; "Input being echoed to the display"... I suggest "bad state" as there are myriad settings and methods that can depart from standard (expected) operation of i/o; 'echo' being but one of those... From memory, it's possible to 'turn off' driver mapping of CR to LF so that the user must type CTRL-J as the EOL character... Good luck! | |
| Dec 9, 2024 at 7:25 | vote | accept | FLAK-ZOSO | ||
| Dec 9, 2024 at 7:21 | comment | added | FLAK-ZOSO | @Chris, the library I mostly use this header with is written in C++, but you're right, that import can be redundant. | |
| Dec 9, 2024 at 7:20 | comment | added | FLAK-ZOSO | @Fe2O3, the "display" is in fact about "output": this "bad state" of the terminal is a state in which I can input characters but I don't see the characters being printed in the terminal at all; however, if I press enter, the typed command gets executed. Thanks for the link, I will give a look to it. | |
| Dec 9, 2024 at 5:53 | comment | added | Chris |
The single thing that appears to make this C++ code vs. C is #include <csdtio>. Is this really necessary vs. #include <stdio.h>?
|
|
| Dec 8, 2024 at 6:16 | history | became hot network question | |||
| Dec 8, 2024 at 2:50 | comment | added | user272752 | "... leaving the terminal unable to display (but not to accept) input ..." Coders must train clients to fully and clearly express themselves. Coders must fully and clearly express themselves, too, setting a good example... I'm gonna guess you mean to say, "leaves the terminal in a bad state", or something similar. The verb "display" usually travels with "output", not "input". | |
| Dec 8, 2024 at 1:37 | comment | added | user272752 | (Not a full answer) I wrote this code to muck around with UI interactivity (for Windows, only) and a bit of VT100 display manipulation. You're welcome to take a look at it. (Sometimes playing with retro can be fun and somewhat educational...) | |
| Dec 7, 2024 at 23:08 | answer | added | G. Sliepen | timeline score: 10 | |
| Dec 7, 2024 at 22:11 | history | edited | toolic | CC BY-SA 4.0 |
deleted 49 characters in body
|
| Dec 7, 2024 at 22:06 | history | asked | FLAK-ZOSO | CC BY-SA 4.0 |