- 24 Jul, 2022 1 commit
-
-
Ömer Fadıl Usta authored
In KF we already looking for 5.15.2 and looking something lower than that is a bit meaningless
-
- 05 May, 2022 1 commit
-
-
Laurent Montel authored
-
- 20 Apr, 2022 1 commit
-
-
Vlad Zahorodnii authored
-
- 19 Apr, 2022 4 commits
-
-
-
Vlad Zahorodnii authored
-
Vlad Zahorodnii authored
-
Vlad Zahorodnii authored
-
- 16 Apr, 2022 1 commit
-
-
Xuetian Weng authored
Basically this is a well known issue in wayland for globals. If bind comes after destroyed, it will raise a invalid global error. The common practice is to delay the destroy of global. Similar technique is also applied to wl_output. CCBUG: 452435
-
- 15 Apr, 2022 1 commit
-
-
Vlad Zahorodnii authored
The API of SurfaceInterface was changed so it always maintains an opaque region. At the surface commit, if the attached buffer is opaque, the whole surface will be marked opaque. Otherwise, the specified opaque region will be intersected with the surface rect.
-
- 13 Apr, 2022 1 commit
-
-
Volker Krause authored
That's a leftover from before resurrecting the qtwaylandscanner fork here for Qt6.
-
- 09 Apr, 2022 1 commit
-
-
Nicolas Fella authored
This allows to get the resource name for XWayland windows, which is useful in the task manager
-
- 08 Apr, 2022 2 commits
-
-
Vlad Zahorodnii authored
If no mode has the current flag set, the first mode object will be announced twice. There's also no benefit from sending the current mode as last. If the current mode changes, the compositor will send the current_mode event, not the mode event. BUG: 452318
-
Vlad Zahorodnii authored
CCBUG: 452318
-
- 05 Apr, 2022 2 commits
-
-
David Edmundson authored
Whilst a subsurface must have a parent at the time of creation, the lifespan is not guaranteed afterwards. It's a weird thing for a client to do, but we need to not crash afterwards. If the parent surface is destroyed we should consider the surface unmapped. BUG: 452044
-
David Edmundson authored
In the current form any client committing multiple times without attaching a buffer would unset the cached state and trigger an error. It's legal (though weird) to commit multiple times before attaching a buffer. We should only reset the state if we commit an empty buffer after having committed an existing buffer. This brings us in line with XdgShell.
-
- 29 Mar, 2022 1 commit
-
-
Vlad Zahorodnii authored
This allows us to simplify rendering code in the compositor.
-
- 18 Mar, 2022 7 commits
-
-
Volker Krause authored
Needed to compile against Qt6.
-
Volker Krause authored
Qt6 QList::operator!= fails to compile otherwise.
-
Volker Krause authored
-
Volker Krause authored
-
Volker Krause authored
This unfortunately clashes with a typedef in a Qt6 header.
-
Volker Krause authored
-
Volker Krause authored
-
- 15 Mar, 2022 2 commits
-
-
Aleix Pol Gonzalez authored
-
Xaver Hugl authored
QVector is much more suitable for modifiers in KWin than QSet, because you can access the underlying array
-
- 11 Mar, 2022 1 commit
-
-
Xaver Hugl authored
If this is not done then KScreen will sometimes unintentionally reset them to the default. BUG: 442520 FIXED-IN: 5.24.4
-
- 03 Mar, 2022 2 commits
-
-
Vlad Zahorodnii authored
Currently, if the pointer surface has to change between two surfaces, the compositor must do the following seat->setFocusedPointerSurface(nullptr); seat->notifyPointerMotion(newPos); seat->setFocusedPointerSurface(focus); The pointer motion is needed so the enter event has correct position, setFocusedPointerSurface(nullptr) is needed to avoid sending a bad motion event before the leave event. This change makes the pointer focus api less error prone by splitting setFocusedPointerSurface() in two functions - notifyPointerEnter() and notifyPointerLeave(). notifyPointerEnter() takes new focus surface as well as the position where the pointer has entered the surface so the focus update can be atomic and without any corner cases. notifyPointerLeave() is used to clear pointer focus.
-
Marco Martin authored
This is needed to cancel drags by pressing Escape which is resposibility of the compositor CCBUG:405267
-
- 02 Mar, 2022 1 commit
-
-
These require Wayland 1.20, for the format definitions.
-
- 23 Feb, 2022 1 commit
-
-
Heiko Becker authored
By using the same EXPORT for ecm_qt_declare_logging_category and ecm_qt_install_logging_categories.
-
- 22 Feb, 2022 1 commit
-
-
Kai Uwe Broulik authored
Don't rely on someone else to pull it in for `close()` Signed-off-by:
Eike Hein <eike.hein@mbition.io>
-
- 21 Feb, 2022 1 commit
-
-
Aleix Pol Gonzalez authored
Consider the cases where we get a touch move or touch up but we never received a touch down before. In the case of move, we'll simulate a touchDown right there and move on with reality. In the case of touch up, we'll just ignore the event as simulating could just be more confusing. BUG: 450338
-
- 12 Feb, 2022 1 commit
-
-
Vlad Zahorodnii authored
xdg_toplevel.configure_bounds() allows to indicate the client the maximum surface size bounds. wayland-protocols: https://gitlab.freedesktop.org/wayland/wayland-protocols/-/merge_requests/41
-
- 10 Feb, 2022 1 commit
-
-
- 27 Jan, 2022 1 commit
-
-
Arjen Hiemstra authored
When dragging from one window to another, we may end up in a data_device that didn't get "data_device_start_drag". In that case, the internal touch point serial will be incorrect and we need to update it to the serial from the seat. The serial stored in the seat is changed to std::optional so we can properly check if it is set.
-
- 25 Jan, 2022 1 commit
-
-
Vlad Zahorodnii authored
The SeatInterface cleans up currentSelection and currentPrimarySelection when the AbstractDataSource::aboutToBeDestroyed() signal is emitted, but since the data source and primary data source have parent objects, they can be potentially destroyed without emitting the aboutToBeDestroyed() signal and thus leaving dangling pointers in SeatInterface. CCBUG: 449101
-
- 14 Jan, 2022 1 commit
-
-
Xaver Hugl authored
DRM_FORMAT_MOD_INVALID is now explicitly included in KWin where needed
-
- 13 Jan, 2022 3 commits
-
-
Heiko Becker authored
...to reflect reality. It already needs kde-primary-output-v1.xml, which appeared in 1.6.0.
-
Jonathan Esk-Riddell authored
GIT_SILENT
-
Jonathan Esk-Riddell authored
GIT_SILENT
-