GitLab

Bump the minimum required version since kwaylandserver cannot be built
with prior versions of wayland-protocols.

Aleix Pol Gonzalez authored Jul 27, 2020 and Aleix Pol Gonzalez committed Jul 28, 2020

Found when running under ASAN

It's been replaced by PipeWire stuff.

SeatInterface cleans up when a data source goes away. However the
cleanup also makes use of metaobjects so needs to run before the leaf
class destructor is run.

All other AbstractDataSource objects emit the unbound signal, which
SeatInterface also connects to do a earlier cleanup. Otherwise we get a
crash if a data control source replaces itself.

Vlad Zahorodnii authored Jul 16, 2020 and Vlad Zahorodnii committed Jul 16, 2020

Rename the aboutToBeUnbound() signal to aboutToBeDestroyed() in order to
make the usage of the word "destroyed" consistent.

Order of a client teardown is:
 - ClientConnection is removed from the static map
 - All our client owned resources are torn down
 - ClientConnection is deleted (via a previous deleteLater)

The recent refactor led to a behavioural change where ::client could
return a null pointer.

We want the client getter to be valid throughout the lifespan of
SurfaceInterface, by doing the lookup once we achieve that.

BUG: 424255

Vlad Zahorodnii authored Jul 07, 2020 and Vlad Zahorodnii committed Jul 08, 2020

Since we don't do wl_display_run(), wl_display_terminate() is pointless.

Vlad Zahorodnii authored Jul 07, 2020 and Vlad Zahorodnii committed Jul 08, 2020

Display::startLoop() isn't used anywhere and it only adds maintenance
burden, so drop it.

Vlad Zahorodnii authored Jul 06, 2020 and Vlad Zahorodnii committed Jul 08, 2020

It can be especially useful if the compositor wants to ensure that all
globals have been created before starting to accept client connections.

Unfortunately, start() and terminate() stuff doesn't align well with it,
so the terminate() method was dropped to ensure that Display always
returns the same wl_display object.

sendStackingOrderChanged() iterates though all clients. Only the new
client needs to be send information at this point.

The main purpose behind the kwaylandserver library is to provide a set
of re-usable wayland compositor extension implementations. However, it's
worth noting that the design of kwaylandserver is far from perfect at
the moment.

KWaylandServer tries to hide all low level wayland details from the
compositor. But it's not the case with buffers, which diminishes the
whole point behind the library.

Creating OpenGL textures from Wayland buffers is the responsibility of
the compositor. So, when it comes to client buffers, we are one foot in
KWaylandServer, and the other foot in the compositor.

Since the surface size is a logical size, the compositor can't use it
for allocating memory for OpenGL textures. This change adds the buffer
size property in SurfaceInterface that can be used for allocating memory
for textures as well as monitoring buffer size changes.

I must say that the introduction of the buffer size property is a crude
hack because BufferInterface just needs to provide an OpenGL texture for
each plane. The main blocker for that is that it would involve moving
the backend, the compositor, and the wayland bits in the same place, for
example kwayland-server or ultimately kwin.

Vlad Zahorodnii authored Jun 19, 2020 and Vlad Zahorodnii committed Jun 24, 2020

The buffer transform is a pretty confusing thing, so document it in
order to avoid misleading people.

Vlad Zahorodnii authored Jun 19, 2020 and Vlad Zahorodnii committed Jun 24, 2020

The buffer scale and the buffer transform property specify transforms
that had been applied to the buffer's contents. Neither one of those
properties apply to the surface, in other words the buffer transform
property doesn't indicate that the surface was rotated or flipped or both.

This change doesn't gain anything in terms of new features, etc. It just
attempts to make things more clear.