wilderjds/kwin - kwin - gitea-jacopods

14155 Commits

36 Branches

0 Tags

96 MiB

Tag: Branch: Tree: 2205c98ec2

Commit Graph

Author	SHA1	Message	Date
Martin Gräßlin	2205c98ec2	Introduce dedicated debug category for everything xkbcommon related	10 years ago
Martin Gräßlin	cb3c6a4780	Implement internal keyboard repeat As a Wayland server KWin does not have to emit additional key repeat events (unlike X11). The clients are responsible for handling this based on the provided key repeat information. Internally KWin needs key repeat, though. E.g. the effects need key repeat (filtering in Present Windows), window moving by keyboard needs repeat, etc. etc. This change introduces the internal key repeat. For each key press a QTimer is started which gets canceled again on the key release. If the timer fires it invoked processKey with a new KeyboardKeyAutoRepeat state. This is handled just like a KeyPress, but states are not updated and the QKeyEvent has autorepeat set to true. The event filters check for the autorepeat state and filter the event out if they are not interested in it. E.g. the filters passing the event to the Wayland client need to filter it out. Currently auto-repeat is bound to using libinput. This needs to be modified. The only backend sending repeated events is X11, thus for other backends it should be enabled. Whether creating a timer on each key event is a good idea is something to evaluate in future. Reviewed-By: Bhushan Shah	10 years ago
Martin Gräßlin	849d17519c	Split keyboard related functionality from InputRedirection Similar to the change regarding pointer and touch a KeyboardInputRedirection is created. The Xkb class is also moved to the new files keyboard_input.h and keyboard_input.cpp. Just like in the case of PointerInputRedirection no signals are added, but the existing signals in InputRedirection are directly invoked.	10 years ago

Author

SHA1

Message

Date

Martin Gräßlin

2205c98ec2

Introduce dedicated debug category for everything xkbcommon related

10 years ago

Martin Gräßlin

cb3c6a4780

Implement internal keyboard repeat

As a Wayland server KWin does not have to emit additional key repeat
events (unlike X11). The clients are responsible for handling this based
on the provided key repeat information.

Internally KWin needs key repeat, though. E.g. the effects need key
repeat (filtering in Present Windows), window moving by keyboard needs
repeat, etc. etc.

This change introduces the internal key repeat. For each key press a
QTimer is started which gets canceled again on the key release. If the
timer fires it invoked processKey with a new KeyboardKeyAutoRepeat state.
This is handled just like a KeyPress, but states are not updated and
the QKeyEvent has autorepeat set to true.

The event filters check for the autorepeat state and filter the event
out if they are not interested in it. E.g. the filters passing the event
to the Wayland client need to filter it out.

Currently auto-repeat is bound to using libinput. This needs to be
modified. The only backend sending repeated events is X11, thus for
other backends it should be enabled.

Whether creating a timer on each key event is a good idea is something to
evaluate in future.

Reviewed-By: Bhushan Shah

10 years ago

Martin Gräßlin

849d17519c

Split keyboard related functionality from InputRedirection

Similar to the change regarding pointer and touch a
KeyboardInputRedirection is created. The Xkb class is also moved to
the new files keyboard_input.h and keyboard_input.cpp.

Just like in the case of PointerInputRedirection no signals are added,
but the existing signals in InputRedirection are directly invoked.

10 years ago

3 Commits (2205c98ec24d52861543cd7e86ca37f76f4e19f8)