-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
virtual-keyboard overrides all keyboard layouts #5134
Comments
The virtual keyboard should definitely not be grouped with something else. |
I've been thinking about how to disable smart grouping specifically for virtual keyboards and there does not seem to be an obvious answer. Matching on "virtual_keyboard" inside sway/input/keyboard.c seems like a rather finicky solution. Perhaps there should be a special "vendor" set for virtual devices, and that can be used for matching? |
Isn't it easy to detect keyboards created with the virtual-keyboard protocol? |
Never mind, there's a special event for it. |
Steps to reproduce:
WLR_BACKENDS=wayland sway
swaymsg -t get_inputs
WAYLAND_DISPLAY=wayland-1 wayvnc --keyboard=is
This does not happen if smart grouping is turned off.
Looking at the debug log, I can see that the virtual keyboard always matches the group of the incumbent keyboard, which ought not happen with different layouts.
I have a theory that because virtual-keyboard sets the layout after it has created (and thus assigned to a group) the group's keyboard layout changes with the virtual keyboard's layout.
The text was updated successfully, but these errors were encountered: