-
Notifications
You must be signed in to change notification settings - Fork 14.7k
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
[libuwac] fix keyboard "sticky" keys when entering window #9725
Conversation
Can one of the admins verify this patch? |
The change seems to be working fine... but I have sometimes the situation, that when I enter a freerdp window and start typing I have some modifier key active and I have to press all modifier keys to have it return to normal state... |
The commit is fixing the following problem: When the freerdp window gets keyboard focus and is notified, it wrongly process keys which are *held*, not a freshly pressed. The comment in the code explains it more.
The commit is fixing the problem when eg. a user is pressing some modifier key to switch from active FreeRDP window and when get back to that window, it "virtually" has that modifier key pressed, thus leading to pressing eg. `Win+r` instead of just `r`.
Hi again, Edit: also added one fix for the scaling code as it is also for uwac |
Fix for a hybrid multimonitor configurations: Previous code was working for me because the display with scale=2 was last on the wayland display list. After restarting it was earlier. To fix this - just take the highest scale provided by a display. Similar as eg. here the SDL is doing: https://github.com/libsdl-org/SDL/blob/b5bc64aa553fe12d09fe2821eace14ea5b948bd9/src/video/wayland/SDL_waylandwindow.c#L1170
@freerdp-bot test |
Refer to this link for build results (access rights to CI server needed): |
Thank you |
The commit is fixing the following problem:
When the freerdp window gets keyboard focus and is notified, it wrongly process keys which are held, not a freshly pressed.
The comment in the code explains it more.