-
Notifications
You must be signed in to change notification settings - Fork 84
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Clarify usage of virtual terminal mode flags #185
Comments
So, the terms "raw" and "cooked" only really apply to the input handle. It looks like an oversight that we implicate any output modes when talking about what is raw vs. what is cooked. 😄 |
When ENABLE_MOUSE_INPUT is set is there a way/function to read the mouse events of mouse movement and button presses from the input buffer? |
When |
I incorporated this guidance into the above PR. |
Hi, I'd like to suggest a few improvements for this page. I learned in the reply here that the ENABLE_PROCESSED_OUTPUT flag should usually be kept enabled when using ENABLE_VIRTUAL_TERMINAL_PROCESSING, even if disabling all the flags that are normally enabled for "cooked" mode. I think I would find it more clear if you mentioned that, both in your discussion at the top of the page about "raw" and "cooked" modes, and in the descriptions of the ENABLE_PROCESSED_OUTPUT and ENABLE_VIRTUAL_TERMINAL_PROCESSING flags.
(Does it still count as "raw" mode if I ENABLE_VIRTUAL_TERMINAL_PROCESSING?)
It might make sense to include a few examples of common scenarios and the flags that would be used in each of them.
Also, in the description of the ENABLE_MOUSE_INPUT flag you mention that the mouse events won't be seen by ReadFile() or ReadConsole() - I think it would be good if you also mentioned a function that could be used to get the mouse events.
Thanks
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
The text was updated successfully, but these errors were encountered: