wilderjds/kwin - kwin - gitea-jacopods

Author	SHA1	Message	Date
Martin Gräßlin	a029300ce5	Rework cursor image handling for Wayland So far updating the cursor image was not really defined. It was possible to use the cursor image from the wayland seat or have a custom set cursor image. But there are no rules in place to decide which one to use when. With this change a dedicated CursorImage class is introduced which tracks the cursor image changes on the seat, on the decoration, in the effects and so on. In addition it tracks which is the current source for the image, that is whether e.g. the cursor from the seat or from effects override should be used. Whenever the cursor image changes a signal is emitted, which is connected to the signal in AbstractBackend. Based on that the backends can directly show the image. The existing code in the backends to install a cursor shape or to install the cursor from the server is completely dropped. For the backend it's irrelevant from where the image comes from. A new feature added is that the cursor image is marked as rendered. This is then passed on to the frame rendered in the Surface and thus animated cursors are finally working. Unfortunately animated cursors are broken in Qt (see https://bugreports.qt.io/browse/QTBUG-48181 ).	10 years ago
Martin Gräßlin	b59593bd9d	Invoke AbstractClient::enterEvent and ::leaveEvent on updating pointer window This implements auto raise and focus follows mouse for Wayland. The decoration interaction needs to be autotested.	10 years ago
Martin Gräßlin	44bb78c193	Map all pointer buttons to Qt::MouseButton The mapping is slightly inspired by the mapping in QtWayland. But the mapping in QtWayland seems wrong. E.g. there is a linux kernel button called BTN_BACK which is not mapped to Qt::BackButton. Anyway we are not really interested in the mapping being 100 % correct for the case in KWin. KWin internally uses only very few mouse buttons and all others are only relevant to figure out whether buttons are pressed. The button code itself is passed to the seat with the native code.	10 years ago
Martin Gräßlin	c044ad98be	Split out pointer related handling from InputRedirection All pointer related code is moved into a new class called PointerInputRedirection. The main idea is to simplify the code and make it easier to maintain. Therefore also a few changes in the setup were performed: * before init() is called, no processing is performed * init() is only called on Wayland and after Workspace is created * init property is set to false once Workspace or WaylandServer is destroyed Thus code can operate on the following assumptions: * Workspace is valid * WaylandServer is valid * ScreenLocker integration is used The various checks whether there is a waylandServer() and whether there is a seat are no longer needed. Some of the checks have been reordered to be faster in the most common use case of using libinput. E.g. whether warping is supported is first evaluated by the variable bound to whether we have libinput and only if that is false the backend is checked. The new class doesn't have signals but invokes the signals provided by InputRedirection. I didn't want to add new signals as I consider them as not needed. The areas in KWin needing those signals should be ported to InputEventFilters.	10 years ago

1 2