https://bugs.kde.org/show_bug.cgi?id=354109
Adam Fontenot <adam.m.fontenot+...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|REPORTED |CONFIRMED
CC| |adam.m.fontenot+kde@gmail.c
| |om
Ever confirmed|0 |1
--- Comment #8 from Adam Fontenot <adam.m.fontenot+...@gmail.com> ---
This issue has seemingly been around since around the time of the switch from
QT4 to QT5. The main issue is here:
https://invent.kde.org/plasma/khotkeys/-/blob/master/kcm_hotkeys/helper_widgets/window_selector.cpp#L36
QT5 passes xinput events here, but the filter only looks for the
XCB_BUTTON_PRESS response type. Proper handling would involve looking for a
XCB_GE_GENERIC response type as well, casting to a xcb_ge_generic_event_t, and
checking that event for the XCB_INPUT_BUTTON_PRESS event type.
I wrote an ugly proof of concept showing that this does fix the basic problem,
but I didn't fully get the feature working again. Among other issues, clicking
on a window that doesn't belong to the KCM seemingly gives a different event
type, and the crosshair cursor is not used over these windows either. Probably
KWin has changed how windows are given access to other windows they don't own,
or something along those lines. Wasn't sure how to investigate this further.
--
You are receiving this mail because:
You are watching all bug changes.
