GitLab

If all outputs have been disconnected, the screensQueried() signal won't
be emitted and Screens::count() and Screens::size() won't be updated.

The signal is not emitted to ensure that kwin is initialized properly when
there are no outputs.

Unfortunately, this breaks repaint scheduling code as it doesn't take
into account that the Screens class may lie in rare cases.

The drm backend should probably create a placeholder screen in case all
physical outputs have been disconnected, but in meanwhile, let's work
around this issue by porting the scene to the output api in the Platform.

Some applications set their own geometry after start,
which overrides the initial rule settings for placement:
position, size and initial placement.

This happens now more often, after introducing the
"Remember app last position" feature for KXMLgui apps.

There is a mechanism to avoid that, by Forcing the rule property
"Ignore geometry", but it is unknown to many users.

This MR adds a hint when some rule properties might not be
respected by the application, so users can set this property
and hopefully avoid bug reports.

BUG: 428781

When an output is disabled, it's not necessarily destroyed.

There should not be any layer shell surfaces on disabled outputs.

According to POSIX [1] that's where it is defined.

[1] https://pubs.opengroup.org/onlinepubs/009604499/basedefs/fcntl.h.html

Improves portability by avoiding the non-standard 'uint'. For example
this fixes building with musl libc:

".../kwin_wrapper.c:45:9: error: unknown type name 'uint';
    did you mean 'int'?"

GIT_SILENT

GIT_SILENT

A situation meant we want to only enable the new keyboard applet by
default on wayland, using the legacy one from the X11 daemon on X11.

We need a unique service name so that we can use DBus activation on it.

GIT_SILENT

This avoids mapping the visible rect between the window local
coordinates and the global coordinates back and forth.

If a service name exists, the relevant object at that path always
should, otherwise it's technically racey due to DBus running in another
thread.

This is needed to make per-screen rendering work correctly.

BUG: 431652

This is needed to make per-screen rendering work correctly.

BUG: 431652

This is needed to make per-screen rendering work correctly.

BUG: 431652

QMap::value() failed to find existing keys when tow ComparablePoint
shared the same x but not the same y.

This commit improves the operator<() to fix that.

Previously code was if socket fd is greater then 0, then we start
process, but new code in 05ebe676 reversed logic. So this
made it not start input method at all.

It's annoying.

As all layouts names are now stored in Property on client side, there is
no need for KeyboardLayoutDBusInterface::getLayoutLongName() method any
more.

warning: c++11 range-loop might detach Qt container (QVector) [clazy-
range-loop]

Adress changes in methods:
- setLayout()
- layoutNames()
- layoutChanged() signal

On that signal, we asquare the new layout anyway all over the places.
Better just pass it along with the signal instead.

Also it's in-line with DBus API signal.

The base handle for layouts in libxkbcommon is an index. Let's follow
this notion in our API to set/get layout, instead of using it's name as
an ID.

On the way, do cleanup. Following methods are removed as not needed any
more:
- Xkb::layoutShortNames()
- Xkb::layoutNames()

If user set custom name for the layout, country flag is not displayed.
Instead, Display Name is shown in the applet.

This reveals shortcomings in current DBus API design.
We need more data to pass over DBus to fix this.
Then, multiple improvements are possible:
- fix aforementioned bug
- add flags to context menu
- display correct translated Layout Name in the context menu
- simpler, cleaner DBus API and applet implementation
- etc.

add EnabledByDefaultFunctionRole in EffectsModel

This fixes a bug where cancelled touch sequences get ignored
which results in stuck touch focus.

With multiple touch devices the slots could interfere

Fix tests regressions introduced in 39a1e11958b1ad47d9a516c1cb4bcea852e92a00

At the moment we are getting the input method from the command line
which is not very handy (but very secure).
This patch changes it so it can be specified from a configuration
setting.

CCBUG: 427972

In case of conflict in i18n, keep the version of the branch "ours"
To resolve a particular conflict, "git checkout --ours path/to/file.desktop"

QOrientationSensor is no longer used by kwin.

If a non-existing variable is used, no warning will be printed.

If the maximizedChanged connection is queued, several configure events
will be sent. If the client acks the first configure event and later on
acks the second one, the maximize animation will be cancelled due to
"unexpected" geometry change.

Based on the code, there is no clear reason why the connection is queued
in the first place.

CCBUG: 431415

Project includes must come first; keep Qt includes together.