-
Notifications
You must be signed in to change notification settings - Fork 120
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
Key::Unicode on MacOS does not behave the same way as on Windows & Linux #307
Comments
If you want to enter text, you should always use the |
The |
@pentamassiv I fixed the issue in my project by replacing the |
Just curious: have you had any luck integrating my change into enigo? It should be easy to use that predefined keycode list, you can fallback to the old system when the provided char doesn't match any of the arms in my code. |
Sorry, I had a look at the code but enigo is supposed to work for all languages and I'm not sure if this won't break it for other languages. I know enigo gets used a lot by many Asian speakers. I did not get the time to investigate this in depth. I've been mostly fixing bugs and trying to finally get the tests in the CI to work to reduced the maintenance burden. |
Describe the bug
On Windows & Linux, calling
enigo.key(Key::Shift, Press)
followed byenigo.key(Key::Unicode("1"), Press)
produces an exclamation mark in a textarea. On MacOS, a number one is produced. This is reproducible only with numbers (shift + any letter produces the expected uppercase letter).Expected behavior
Holding shift and a number should produce the special character associated with that combination regardless of the OS.
Environment
The text was updated successfully, but these errors were encountered: