- 04 Mar, 2021 1 commit
-
-
Nicolas Fella authored
As discussed in https://mail.kde.org/pipermail/plasma-devel/2021-February/119329.html GIT_SILENT
-
- 01 Mar, 2021 1 commit
-
-
Aleix Pol Gonzalez authored
There's a good chance the user still cares about it. They're free to ignore it if they want.
-
- 25 Feb, 2021 1 commit
-
-
David Edmundson authored
This is mostly all automatic from clazy, though it got confused by a few namespace issues.
-
- 23 Feb, 2021 1 commit
-
-
Vlad Zahorodnii authored
Bump the required C++ version to C++17, similar to other Plasma projects. This opens us things such as std::optional, etc.
-
- 17 Feb, 2021 4 commits
-
-
Vlad Zahorodnii authored
If the surface already has keyboard focus, do nothing.
-
Vlad Zahorodnii authored
We need to send out these events; otherwise the client may have incorrect state for the new wl_keyboard object.
-
Vlad Zahorodnii authored
-
Vlad Zahorodnii authored
-
- 16 Feb, 2021 1 commit
-
-
David Edmundson authored
During a drag the source can disappear at any time. The other client will be notified, but it may have actions in flight. Other methods were guarded but not data_offer_finished.
-
- 15 Feb, 2021 1 commit
-
-
Vlad Zahorodnii authored
Currently, the compositor is supposed to pass the position of the touch point to the touchDown() function and in return get its unique global id. The id can be be passed to subsequent touchMotion() and touchUp(). The compositor is responsible for mapping between libinput slots and internal touch point ids. The mapping step is unnecessary and adds in some complexity as the input code now has to keep the mapping table up to date. This change makes the touch API more convenient to use by making relevant functions take touch ids that are assigned by the compositor. Usually, compositor would use libinput_event_touch_get_seat_slot() to get touch ids. It also allows introducing event objects that can be useful later in the future.
-
- 11 Feb, 2021 1 commit
-
-
Vlad Zahorodnii authored
At the moment, it is possible to crash the compositor if some client sets a buffer scale less than 1.
-
- 02 Feb, 2021 2 commits
-
-
David Edmundson authored
-
Vlad Zahorodnii authored
The new method can be used to check if the surface has a pending frame callback. CCBUG: 428499
-
- 30 Jan, 2021 1 commit
-
-
Nicolas Fella authored
This makes it easier to build against both Qt5 and Qt6 GIT_SILENT
-
- 29 Jan, 2021 1 commit
-
-
Vlad Zahorodnii authored
With the local copy of qtwaylandscanner, it's possible now to simplify handling of inert sub-surfaces.
-
- 26 Jan, 2021 2 commits
-
-
Vlad Zahorodnii authored
This makes it easier to analyze logs.
-
David Edmundson authored
This is a copy of the code from Qt5.15 with some backported patches from development branch of Qt. One of the upcoming fixes introduces new API, which is why we can't rely on distro packaging. The cmake macro is mostly copied from ECM, but set to rebuild generated code when the scanner changes.
-
- 21 Jan, 2021 4 commits
-
-
Vlad Zahorodnii authored
-
Jonathan Riddell authored
GIT_SILENT
-
Jonathan Riddell authored
GIT_SILENT
-
Jonathan Riddell authored
GIT_SILENT
-
- 12 Jan, 2021 1 commit
-
-
David Edmundson authored
The following order of events are legal: Typically order is: - server announces a new output - client binds to a new output - server updates the surface to be on new output But we can have events occur in the following order: - server announces a new output - server updates the surface to be on new output - client binds to a new output At which point when we update the surface there is no ID to tell the client which output the surface is on. This patch watches for clients binding to output and updates appropriately.
-
- 06 Jan, 2021 4 commits
-
-
Aleix Pol Gonzalez authored
Be more explicit about the types, prefer passing semantically correct parents and keep track of the pads from the object rather than relying on them being initialised properly.
-
Aleix Pol Gonzalez authored
-
Aleix Pol Gonzalez authored
Namely TabletPadV2Interface, TabletPadRingV2Interface, TabletPadStripV2Interface and TabletPadGroupV2Interface were entirely missing.
-
Aleix Pol Gonzalez authored
Add an m_removed attribute to all elements that can send a removed event. Never advertise an object that has been marked as removed already.
-
- 05 Jan, 2021 1 commit
-
-
Jan Blackquill authored
-
- 16 Dec, 2020 1 commit
-
-
Aleix Pol Gonzalez authored
Add missing & Remove unnecessary namespace Consistant m_ prefix
-
- 14 Dec, 2020 2 commits
-
-
Andrey Butirsky authored
We send modifiers to the active client when they change, and when we focus an existing client we send the cached state. For this reason it's important we always update our internal store of modifiers regardless of whether a surface is currently active. Unit test is adopted accordingly. BUG: 429930
-
Vlad Zahorodnii authored
The main reason why we have factory methods is that up to some point, kwayland had its own signal to indicate when globals have to be removed. Now that all globals add destroy listeners for the wl_display object, we don't have that signal. Most factory methods are equivalent to doing new T(display). Besides adding unnecessary boilerplate code, another reason to get rid of the factory methods is to reduce the amount of merge conflicts. If several persons work on implementing wayland protocols at the same time, sooner or later someone will have to resolve merge conflicts in Display.
-
- 12 Dec, 2020 1 commit
-
-
Xaver Hugl authored
-
- 09 Dec, 2020 3 commits
-
-
Vlad Zahorodnii authored
LICENSES directory contains full description of every license that is used in kwayland-server.
-
Vlad Zahorodnii authored
-
Vlad Zahorodnii authored
libwayland-server allows the wl_display accept client connections on more than one socket. We currently don't listen on multiple sockets, but it would be nice if Display supported such operation mode.
-
- 07 Dec, 2020 1 commit
-
-
adrien faveraux authored
-
- 01 Dec, 2020 1 commit
-
-
adrien faveraux authored
-
- 27 Nov, 2020 1 commit
-
-
Vlad Zahorodnii authored
-
- 19 Nov, 2020 1 commit
-
-
Bhushan Shah authored
And make them public in th keyboard_interface, there's no point in wrapping this in seat_interface with new approach See also: #13
-
- 17 Nov, 2020 2 commits
-
-
Aleix Pol Gonzalez authored
Otherwise they wouldn't notice and wouldn't update to the settings of the new output, like the new output's scaling.
-
David Edmundson authored
A threshold exists to stop users flooding the server for no reason. However, there is a usecase for small timeouts. rsibreak has a "please relax for 20 seconds" interface. Here it makes perfect sense to know if a user is active in small increments. The plan is to start a 1s timer and wait for that. Then we wait locally for 20s without a resume event.
-