-
Notifications
You must be signed in to change notification settings - Fork 8.4k
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
Partially fix mapping of virtual keys to characters #2836
Conversation
@carlos-zamora I believe your review comments should be addressed now. 🙂 |
I believe the tests are failing due to some recent commit in master? I don't think I caused these issues. |
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
This pull request has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 7 days. It will be closed if no further activity occurs within 7 days of this comment. |
@zadjii-msft @DHowett-MSFT This PR just got a |
Ah, my comment removed the tag. 😄 Anyways… Do you know when (or if) this will be merged? |
Whoops, that's on us. I think we were holding it since we were about to release v0.5, but now that 0.5 is out, let's get this in :) |
🎉 Handy links: |
Summary of the Pull Request
This PR mostly fixes the mapping of Alt combinations to unicode characters.
The case of AltGr was originally hotfixed by returning early in
TerminalControl
.But this didn't fix e.g. AltShift combinations. See #2771 for instance.
This PR now fixes this particular remaining issue.
Cases where a single keypress generates more than a single UTF-16 code point (e.g. when diacritics come into play) are not fixed though, due to a limitation in the design of the low level
KeyEvent
class.PR Checklist
ITerminalInput
interfaceDetailed Description of the Pull Request / Additional comments
This removes the special handling of AltGr in
TerminalControl
, so thatterminalInput
may now handle it by itself.I believe it'd be nice to extend
InputTest.cpp
to include a test for the translation of Shift. to ">", but unfortunately this would be exclusive to US keyboard layouts.My german keyboard layout for instance uses Shift< for this (there's a dedicated "<" key).
How would I build a unit test for this that works independent of "internationalization"?
Validation Steps Performed
-> Ensured that AltGr combinations still work.