Create Task
Maniphest T4454

[frameworks] KModifierKeyInfo needs porting
Closed, ResolvedPublic
Actions

Description

A possibility to fix this is:

  1. Implement a plugin infrastructure for the platforms
  1. Add a Wayland sepcific plugin

2a) Wayland specific plugin built on top of KWayland using a KWayland::Client::Seat and a Keyboard and Pointer on the Seat so that it can track all key presses (on the application) and all pointer events
2b) Use xkbcommon to figure out which modifiers are pressed

See also https://bugs.kde.org/show_bug.cgi?id=370454

sitter added a project: Plasma on Wayland.Nov 7 2016, 1:40 PM
sitter added a subscriber: sitter.
hein added a subscriber: hein.May 7 2017, 10:59 PM

I was looking into this ...

Tracking all key presses wouldn't get us /initial/ state at connection time, though? The lock screen (where this is used) would need that.

How about we instead expose the modifier state on the InputDevice D-Bus interface in kwin (or add a new interface with it) and add a kwin-specific backend to KModifierKeyInfo that just uses D-Bus as dep?

hein added a subscriber: graesslin.May 8 2017, 12:06 AM
davidedmundson moved this task from Peripheral to Done on the Plasma on Wayland board.Sep 11 2019, 8:43 AM
davidedmundson assigned this task to apol.
davidedmundson updated the task description. (Show Details)
romangg closed this task as Resolved.Sep 16 2019, 12:10 PM