wilderjds/kwin - kwin - gitea-jacopods

15290 Commits

36 Branches

0 Tags

96 MiB

Tag: Branch: Tree: 207eb167e1

Commit Graph

Author	SHA1	Message	Date
Martin Gräßlin	cc2f4e3240	Support for relative pointer motion events Summary: If KWin interacts with Libinput the RelativePointerManager interface gets created on the Wayland server. The ForwardInputEventFilter does forward the relative motion events in addition to the normal motion events. In order to properly support the relative motion events as they are expected by the Wayland protocol the handling of pointer motion events got slightly adjusted: * Libinput Pointer event extended by the additional data points * Libinput Pointer event carries the delta as a QSizeF instead of QPointF * PointerInputRedirection adjusted to take a pointer motion event with more arguments * Custom QMouseEvent subclass adjusted to carry the additional members The DebugConsole is adjusted to show the relative motion events in addition to the global position. Test Plan: Verified the manager object is created and verified the events in DebugConsole. Unfortunately not aware of any test application. Reviewers: #kwin, #plasma_on_wayland Subscribers: plasma-devel, kwin Tags: #plasma_on_wayland, #kwin Differential Revision: https://phabricator.kde.org/D2979	10 years ago
Martin Gräßlin	69cbb40903	Pass LibInput::Device* through the event handlers Summary: The signals emitted by LibInput::Connection carry the Device for which the input event was received. This Device is passed to the input handlers. Custom event classes are added which extend QMouseEvent, QKeyEvent and QWheelEvent respectively and expose the Device. The Device is only passed around as a forward declared pointer, so even if compiled without libinput support, it should still compile. Event handlers which need to get access to the Device can now just cast the event pointer to the custom class and access it. This can be used in future to handle device specific key codes, etc. As we don't have a proper event classes for touch events the event handlers do not yet have access to the Device. Here the internal API needs to be adjusted in future. Reviewers: #plasma Subscribers: plasma-devel Tags: #plasma Differential Revision: https://phabricator.kde.org/D1667	10 years ago

Author

SHA1

Message

Date

Martin Gräßlin

cc2f4e3240

Support for relative pointer motion events

Summary:
If KWin interacts with Libinput the RelativePointerManager interface
gets created on the Wayland server. The ForwardInputEventFilter does
forward the relative motion events in addition to the normal motion
events.

In order to properly support the relative motion events as they are
expected by the Wayland protocol the handling of pointer motion events
got slightly adjusted:
* Libinput Pointer event extended by the additional data points
* Libinput Pointer event carries the delta as a QSizeF instead of
QPointF
* PointerInputRedirection adjusted to take a pointer motion event with
more arguments
* Custom QMouseEvent subclass adjusted to carry the additional members

The DebugConsole is adjusted to show the relative motion events in
addition to the global position.

Test Plan:
Verified the manager object is created and verified the
events in DebugConsole. Unfortunately not aware of any test application.

Reviewers: #kwin, #plasma_on_wayland

Subscribers: plasma-devel, kwin

Tags: #plasma_on_wayland, #kwin

Differential Revision: https://phabricator.kde.org/D2979

10 years ago

Martin Gräßlin

69cbb40903

Pass LibInput::Device* through the event handlers

Summary:
The signals emitted by LibInput::Connection carry the Device for which
the input event was received. This Device is passed to the input handlers.

Custom event classes are added which extend QMouseEvent, QKeyEvent and
QWheelEvent respectively and expose the Device. The Device is only passed
around as a forward declared pointer, so even if compiled without libinput
support, it should still compile.

Event handlers which need to get access to the Device can now just cast
the event pointer to the custom class and access it. This can be used in
future to handle device specific key codes, etc.

As we don't have a proper event classes for touch events the event
handlers do not yet have access to the Device. Here the internal API
needs to be adjusted in future.

Reviewers: #plasma

Subscribers: plasma-devel

Tags: #plasma

Differential Revision: https://phabricator.kde.org/D1667

10 years ago

2 Commits (207eb167e1f4107db06c44dc6b633b94e359c156)