-
Notifications
You must be signed in to change notification settings - Fork 171
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
Issue 720: Spanish Keyboard Layout Accents #721
base: master
Are you sure you want to change the base?
Conversation
This comment has been minimized.
This comment has been minimized.
Codecov Report
@@ Coverage Diff @@
## master #721 +/- ##
==========================================
+ Coverage 21.17% 21.28% +0.10%
==========================================
Files 73 73
Lines 28137 28181 +44
==========================================
+ Hits 5958 5998 +40
- Misses 22179 22183 +4
Continue to review full report at Codecov.
|
Sorry for the huge delay here. Is there any chance you could do some testing with the current iteration? I am not familiar with these keyboard layouts... It is working to the best of my knowledge (and my knowledge is not much haha). Each OS has slightly different behavior here. It would be great to get a sanity check from someone familiar with these keys. Could you pay explicit attention to I observed the following non-working key events: neovim-qt/test/tst_input_common.cpp Lines 291 to 297 in 6218900
However, this could just be a layout mis-configuration... Linux/Windows behave differently from my MacOS Spanish layout. |
Sadly I don't have access to my Macbook. My country has limited mobility due to COVID so until the restrictions are lifted I can't pick it up :( |
Sorry to hear that :( I can relate. Here in the Northeastern States we were hit hard early and had aggressive shutdowns. No fun, strange times... Let me know when you're able to test. The changes are ready for check-in pending validation. Any additional patching will be quick and easy. |
Friendly ping. I hope the COVID situation has improved for you! |
f33d5a7
to
7487dee
Compare
Codecov Report
@@ Coverage Diff @@
## master #721 +/- ##
==========================================
- Coverage 22.75% 22.09% -0.66%
==========================================
Files 81 74 -7
Lines 29031 28385 -646
==========================================
- Hits 6606 6273 -333
+ Misses 22425 22112 -313
Continue to review full report at Codecov.
|
Do you have the ability to test this on MacOS again? This should be ready for merge, but I'm not familiar with the Spanish keyboard layout. It would be good to have a native user test this before I hit the merge button. Thanks! |
Hi @jgehrig Sorry for the HUGE delay. I've been away from home for most of the year without any access to a Mac. Now I'm back at home for a few days; I'll test it this afternoon (about 12 hours from now) and let you know. |
Hi @jgehrig I've tested again and some of the key combinations that failed on my previous tests are now working, but other seems to still be broken:
'ESC' means that it behaves like pressing escape; it puts you into normal mode. I got weird messages when compiling so I'm not 100% sure this is not a problem with my compilation. I'm taking the Mac this time so count on me for any retests. |
Excellent. Thank you very much! That table is very helpful. One quick ask: can you add a I just modified the PR to include some additional diagnostics for Debug builds ( Additional Table Column:
The Alternatively, if it is too hard to pick out the specific events, you can copy/pipe the output to a
With the new diagnostics, it should be easier to identify the specific key; Very likely
Let's see the build logs, just to be extra cautious. You should be able to drag/drop the log file into your comment. Can you copy-paste the logs into a *.txt file?
Awesome! Thanks 👍 Hopefully we can get this fixed quickly. |
Here's the table with the QKeyEvent data:
The build log looks good but I'm attaching it just in case. I think yesterday I mistook the brew install log for the build log. |
I wish Qt had a better mechanism for detecting keyboard layout/localization... The remaining issues are We'll need to carefully pick behavior that minimizes negative impact across layouts. Probably disallow |
Maybe, but I'm not sure if that would break other layouts :( |
It will (to some degree). My |
Accent characters are not handled correctly for the Spanish Keyboard Layout. TODO Adding tests only, not sure if these are correct... TODO Fix For Windows. Validate MacOS/Linux
Issue #720: The
[
character is not handled properly on Spanish Keyboard Layouts.The Spanish Layout contains keys like ` and &. These keys add an accent to the next character typed.
For example:
Supporting this input mode will be interesting and may not be possible without adding state to
NeovimQt::Input::convertKey
.