Skip to content
This repository has been archived by the owner on Jan 4, 2023. It is now read-only.

[Key not natively supported]: "ñ" #49

Closed
luisg123v opened this issue Sep 18, 2016 · 5 comments
Closed

[Key not natively supported]: "ñ" #49

luisg123v opened this issue Sep 18, 2016 · 5 comments
Labels
Milestone

Comments

@luisg123v
Copy link

I noticed that, apparently, the "ñ" key, available in Spanish keyboards (as in "español") is not natively supported by AntiMicro

When I press that key within KeyChecker, I get the following:

Event Handler:        XTest
Native Key Value:     0xf1
Qt Key Value:         0xd1
antimicro Key Value:  0x0

Here is a screenshot of my KeyChecker
antimicro-key not detected

I'd like to add that the key is recognized and works just fine.

jsbackus added a commit that referenced this issue Sep 18, 2016
@jsbackus
Copy link
Member

Oh no! Yes, looking at the code it looks like there are several missing keys for non-US keyboards. You're clearly running on a Linux machine. Would you try a couple of things for me, please?

  1. Build and try the version here
  2. Build either the official 2.22 or the above with uinput and try the key checker on it (you'll need to start it with --eventgen uinput).

Thanks!

@jsbackus jsbackus added the bug label Sep 18, 2016
@jsbackus jsbackus added this to the 2.23 milestone Sep 18, 2016
@luisg123v
Copy link
Author

Hi, thanks for the quick reply!

Request 1:
I've compiled and run the version you provided and got the following results:

Event Handler:        XTest
Native Key Value:     0xf1
Qt Key Value:         0xd1
antimicro Key Value:  0xf1

As you can see, the antimicro Key Value is the same as the Native Key Value. I don't know if that was the desired output, since the antimicro Key Value usually is the same as the Qt Key Value.

Request 2:
I compiled the version you provided using the DWITH_UINPUT=ON flag, as suggested in BuildOptions.md. I got the following output:

Event Handler:        uinput
Native Key Value:     0x0
Qt Key Value:         0xd1
antimicro Key Value:  0x0

Same pattern here. To make uinput to work, I had to either run antimicro as root or change the owner of /dev/uinput from root to myself. Is that normal?

On the oter hand, the --eventgen option seems not to be documented anywhere. Is it an internal option used only for debuggin?

jsbackus added a commit that referenced this issue Sep 21, 2016
…racters correctly. Mapping to capitals... Hopefully addresses issue #49.
@jsbackus
Copy link
Member

Thanks! Yes, I was afraid that uinput doesn't support the extended characterset. Not sure where things stand with it, so I wanted to try it. Thanks!

Yikes! Looks like the issue is that Qt doesn't have a mapping for the small-case Latin characters. Please try to build the version here.

@luisg123v
Copy link
Author

Now, the antimicro Key Value is the same as the Qt one:

Event Handler:        XTest
Native Key Value:     0xf1
Qt Key Value:         0xd1
antimicro Key Value:  0xd1

and, if I use uinput, I get the following output:

Event Handler:        uinput
Native Key Value:     0x0
Qt Key Value:         0xd1
antimicro Key Value:  0x0

@jsbackus
Copy link
Member

@luisg123v Thanks! Sounds like the updated program works for you in X mode. I've made a separate issue (#57) to track the potential problem with uinput, since I don't know that it is actually an issue for anyone.

Since it looks like the fix addresses your issue, I'm going to close it. Please feel free to re-open if you have additional concerns. Thanks for your help!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants