kwin/plugins/platforms/virtual
Martin Gräßlin d0c488f4a2 Announce output changes to Wayland for platforms not handling outputs
Summary:
Most platforms like the nested and virtual do not handle the outputs
themselves and WaylandServer announces the Outputs to Wayland.

So far this was static: at startup it got announced once to Wayland
and any changes were not catched.

This change makes WaylandServer listen to changes to the Screens and
sync them to Wayland.

Unfortunately KWin's internal Screen information is not sufficient to
properly synchronize this to Wayland and also Wayland by not supporting
adding/removing modes does not help.

Thus the solution implemented here is to add new outputs reflecting the
changes and then removing the old ones. This creates situations with more
outputs being present than actually there, but prevents that there are
no outputs at all.

Test Plan: Auto test added which verifies this for the virtual platform

Reviewers: #kwin, #plasma_on_wayland

Subscribers: plasma-devel, kwin

Tags: #plasma_on_wayland, #kwin

Differential Revision: https://phabricator.kde.org/D2233
2016-07-20 13:53:02 +02:00
..
CMakeLists.txt
egl_gbm_backend.cpp
egl_gbm_backend.h
scene_qpainter_virtual_backend.cpp Paint the software cursor directly in SceneQPainter 2016-06-29 08:50:46 +02:00
scene_qpainter_virtual_backend.h Paint the software cursor directly in SceneQPainter 2016-06-29 08:50:46 +02:00
screens_virtual.cpp Announce output changes to Wayland for platforms not handling outputs 2016-07-20 13:53:02 +02:00
screens_virtual.h
virtual.json
virtual_backend.cpp [platforms] Call setSoftWareCursor in init instead of ctor 2016-06-29 08:48:24 +02:00
virtual_backend.h