diff options
| author |  Kenny Levinsen <kl@kl.wtf> | 2022-12-04 01:20:06 +0100 |
|---|---|---|
| committer |  Simon Ser <contact@emersion.fr> | 2022-12-12 11:26:11 +0100 |
| commit | 817f1bbec3cec1657d0e92714f883faa45a6fef7 (patch) | |
| tree | 2209393661635bb54462db782ed1a8a4e0dd407c /swaybar | |
| parent | build: bump version to 1.8-rc2 (diff) | |
| download | sway-817f1bbec3cec1657d0e92714f883faa45a6fef7.tar.gz sway-817f1bbec3cec1657d0e92714f883faa45a6fef7.tar.zst sway-817f1bbec3cec1657d0e92714f883faa45a6fef7.zip | |
seat: Avoid sending redundant keymaps on reload
When we reload the config, we reset every input device and re-apply
configuration from the config file. This means that the keyboard keymap
is updated at least once during config reload, more if the config file
contains keyboard configuration.
When they keyboard keymap changes and is updated through wlr_seat, the
keymap ends up sent to every keyboard bound in every client, seemingly
multiple times. On an x230 of mine with a keyboard layout set in the
config file, I see 42 keymap events sent to foot on config reload.
Reduce events from keyboard configurations by skipping all but the
currently active keyboard for the seat, and by clearing the active
keyboard during input manager device reset. After this change, I only
see a single just-in-time keymap event.
Fixes: https://github.com/swaywm/sway/issues/6654
Diffstat (limited to 'swaybar')
0 files changed, 0 insertions, 0 deletions