wilderjds/kwin - kwin - gitea-jacopods

Author	SHA1	Message	Date
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
Martin Gräßlin	60783b8228	Touch support in libinput	11 years ago
Daniel Pastushchak	0d997b1093	Introduce categorized logging for kwin core Done by Daniel Pastushchak for KDE during GCI-2014.	11 years ago
Martin Gräßlin	a918591fef	Use Logind to open/close devices needed by libinput With libinput we have the problem that we need to have privileges to open the device files. In order to not need wrappers or suid bits, we use logind. This means that kwin_wayland has to be the session controler. A LogindIntegration is added to connect to logind and wrap the dbus calls. This is based on the logind integration done for ksld in ksmserver. The LogindIntegration is started by Workspace and the InputRedirection tries to become the session controller and starts the libinput integration only after this succeeded.	12 years ago
Martin Gräßlin	c4bb3d11fc	Initial support for libinput Libinput is an optional dependency for getting low level input events. As opening the input devices requires root privs this is rather pointless in the current state. But there is a small added test app which can be executed with root privs to demonstrate the functionality. To properly get input events we need a wrapper like it's used in weston. So far the following is setup: * opening devices found by udev * forwarding keyboard events to InputRedirection * forwarding pointer button events to InputRedirection * forwarding pointer axis events to InputRedirection * signals emitted for pointer motion events Pointer motion events need some further work as they are provided as delta events. We need to track that and map them properly. Also missing are touch events due to me not having a touch screen. It should be fairly simple to setup the touch events, though. Also hotplugging of devices is not yet implemented.	12 years ago