-
Notifications
You must be signed in to change notification settings - Fork 893
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
ReceivedCharacter
no longer emitted on Windows for Alt+key since PR#2445
#2504
Comments
Yes this was kind of intentional based on the Windows documentation and how these
|
I think the right way would be to revert that for now? Given that it's causing portability issues and causing issues downstream? The right fix for that would be a keyboard v2 API? What do you think @msiglreith ? |
I mean we can forward the
|
The issue is that we need Right now I don't see a way to fix the issue in alacritty, since we need characters to handle alt bindings. |
Created a workaround for now in #2505 based on the 3rd approach - please verify if this is works for alacritty |
Another possibility is to intercept |
Looking at #2505 I started wondering if it might be possible to provide the necessary customization without a larger change in the API. On Windows, as I am not familiar with
Not sure if this is really the best API design. It still needs a breaking change, as #2505 as proposed will actually both deliver |
Thank you for the fix! |
In #2445 a change was made, affecting only Windows, to spot sending
ReceivedCharacter
in response toWM_SYSCHAR
messages, orAlt+key
combination.This creates a discrepancy between Windows and other platforms. As on other platforms,
ReceivedCharacter
is still sent whenAlt+b
is pressed, for example.Alacritty is one of the applications that use
winit
and is negatively affected by this change.See this issue for Alacritty specific discussion: alacritty/alacritty#6356
Was this intentional that
Alt+key
is no longer sendingReceivedCharacter
and other platforms will be updated similarly, or was it an accident?The text was updated successfully, but these errors were encountered: