Skip to content

Conversation

@xi
Copy link
Contributor

@xi xi commented Sep 1, 2025

Fixes #4101, #4184, and potentially some others. This also has the potential to replace the language modules for sway, hyprland, and niri.

As a first step, I re-implemented the keyboard-state module to use the keyboard information provided by wayland rather than libinput. In a second step, I added layout detection based on that same information.

This works for me (on labwc), but at the same time it sounds too good to be true. So there might well be a huge downside to this approach that I am not aware of.

Currently this is a rough draft and could use some cleanup. But I wanted to get feedback on the general approach before spending too much time.

@xi xi force-pushed the keyboard-state-layout branch from cec4b5c to 72f872f Compare September 1, 2025 13:34
@xi xi force-pushed the keyboard-state-layout branch from 72f872f to 03d4b00 Compare September 1, 2025 13:38
@xi xi force-pushed the keyboard-state-layout branch from 03d4b00 to a2cd205 Compare September 1, 2025 13:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Keyboard layout module for labwc

1 participant