-
Notifications
You must be signed in to change notification settings - Fork 243
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
deadkeys #42
Comments
Yeah is there any way to detect when user pressed a deadkey to possibly be composing a combined character? We have a lot of those in Icelandic and none seem to work, so far I've tried |
Okay I just figured out I can use |
Thank you for your report. I will look into the issue with disappearing second characters shortly. @logileifs Did you paste the code correctly? You seem to be joining a grave accent (`) with an e, which should indeed produce è. |
Silly mistake of me, you're absolutely right, I was using the wrong one. One question though, does pynput provide any information on when a dead key is pressed? Or is it just treated as any other alphanumeric character? |
Logileifs, can you show me how exactly to use KeyCode.from_dead? |
@SpecialCharacter just exactly like I posted in the comment above. You put your dead key in |
The problem is that I need something like
But how do I print it? I suppose with keyboard.type? |
|
@logileifs it does not work for me :( |
well I had not tried it in action yet, only in the interactive interpreter. I just assumed I could catch the deadkeys with something like
I'll try it out and report back how it goes |
@SpecialCharacter I can confirm that it's working for me with the logic above. It's just some pseudo code with the important bits from my code but if you need further clarification I can post some actual samples from my code, just let me know |
@SpecialCharacter Did the solution provided by @logileifs help you? |
Unfortunately no :(
The character I type after the deadkey is not registered in the memory.
Otherwise it should work.
Am 23.08.2017 um 21:00 schrieb moses-palmer:
…
@SpecialCharacter <https://github.com/specialcharacter> Did the
solution provided by @logileifs <https://github.com/logileifs> help you?
|
Also, now I get a name error: |
You will have to import |
Ups… thank you!
|
Still not working :(
key ['´'] released [acute] I type: `m Why does pynput do the acute when I type the grave? |
OK, now the code ALMOST works - if I delete |
@logileifs By the way, your m̀ code works! |
Hi, has somebody come up with a solution how to make the virtual dead key visible to pynput? |
Oh, and also Windows splits again ` (grave) into:
This behaviour is very annoying. Can you think of a way to fix it? I mean, there is a difference between m and M, so why not between ` (grave) and ´ (acute)? |
Hi again… so has somebody come up with a solution how to make the virtual dead key (not visible to pynput) into a real dead key? It works in Autohotkey, so why not in Python? |
The deadkeys are still not working 100% correctly, I think.
Let's say I want to turn `M into M̀ (a combined character).
But that does not function because there is no character M̀ (at least not in my keyboard layout), so the deadkey remains virtual, until I type a second character (which is ignored in the memory) and the deadkey appears on my screen together with the second character.
I don't know if there is a way to fix this.
What I want to have is the second character not being ignored in the memory.
Also, when I type the deadkey twice, while on my screen the characters are `` (down, down), they are ´` (up, down) in the memory.
I think that is odd...
The text was updated successfully, but these errors were encountered: