Script 'mail_helper' called by obssrc
Hello community,
here is the log from the commit of package plasma-wayland-protocols for
openSUSE:Factory checked in at 2021-09-08 21:36:18
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Factory/plasma-wayland-protocols (Old)
and /work/SRC/openSUSE:Factory/.plasma-wayland-protocols.new.1899 (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Package is "plasma-wayland-protocols"
Wed Sep 8 21:36:18 2021 rev:5 rq:916943 version:1.4.0
Changes:
--------
---
/work/SRC/openSUSE:Factory/plasma-wayland-protocols/plasma-wayland-protocols.changes
2021-05-05 20:39:06.987144013 +0200
+++
/work/SRC/openSUSE:Factory/.plasma-wayland-protocols.new.1899/plasma-wayland-protocols.changes
2021-09-08 21:36:21.765870822 +0200
@@ -1,0 +2,11 @@
+Sun Sep 5 13:32:15 UTC 2021 - Fabian Vogt <fab...@ritter-vogt.de>
+
+- Update to 1.4.0:
+ * Add set_frost to contrast protocol
+ * outputdevice, outputmanagement: add rgb range setting
+ * Add kde_kwin_output_device_mode_v2 to handle output modes
+ * org_kde_plasma_window_management: Allow sending windows to an output
+ * Decouple activation feedback from window management
+ * plasma-window-management: allow to report which apps are starting
+
+-------------------------------------------------------------------
Old:
----
plasma-wayland-protocols-1.3.0.tar.xz
plasma-wayland-protocols-1.3.0.tar.xz.sig
New:
----
plasma-wayland-protocols-1.4.0.tar.xz
plasma-wayland-protocols-1.4.0.tar.xz.sig
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Other differences:
------------------
++++++ plasma-wayland-protocols.spec ++++++
--- /var/tmp/diff_new_pack.TWBAgy/_old 2021-09-08 21:36:22.217871348 +0200
+++ /var/tmp/diff_new_pack.TWBAgy/_new 2021-09-08 21:36:22.221871352 +0200
@@ -18,10 +18,10 @@
%bcond_without lang
Name: plasma-wayland-protocols
-Version: 1.3.0
+Version: 1.4.0
Release: 0
Summary: Wayland protocols used by Plasma
-License: LGPL-2.1-only AND LGPL-2.1-or-later AND MIT AND BSD-3-Clause
+License: BSD-3-Clause AND LGPL-2.1-only AND LGPL-2.1-or-later AND MIT
Group: System/GUI/KDE
URL: https://www.kde.org
Source0:
https://download.kde.org/stable/%{name}/%{name}-%{version}.tar.xz
++++++ plasma-wayland-protocols-1.3.0.tar.xz ->
plasma-wayland-protocols-1.4.0.tar.xz ++++++
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn'
'--exclude=.svnignore' old/plasma-wayland-protocols-1.3.0/CMakeLists.txt
new/plasma-wayland-protocols-1.4.0/CMakeLists.txt
--- old/plasma-wayland-protocols-1.3.0/CMakeLists.txt 2021-05-01
02:47:37.000000000 +0200
+++ new/plasma-wayland-protocols-1.4.0/CMakeLists.txt 2021-09-05
02:04:39.000000000 +0200
@@ -1,6 +1,6 @@
cmake_minimum_required(VERSION 3.5)
-project(PlasmaWaylandProtocols VERSION 1.3.0)
+project(PlasmaWaylandProtocols VERSION 1.4.0)
include(FeatureSummary)
include(CMakePackageConfigHelpers)
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn'
'--exclude=.svnignore' old/plasma-wayland-protocols-1.3.0/src/CMakeLists.txt
new/plasma-wayland-protocols-1.4.0/src/CMakeLists.txt
--- old/plasma-wayland-protocols-1.3.0/src/CMakeLists.txt 2021-05-01
02:47:37.000000000 +0200
+++ new/plasma-wayland-protocols-1.4.0/src/CMakeLists.txt 2021-09-05
02:04:39.000000000 +0200
@@ -9,6 +9,8 @@
protocols/keystate.xml
protocols/outputdevice.xml
protocols/output-management.xml
+ protocols/kde-output-device-v2.xml
+ protocols/kde-output-management-v2.xml
protocols/plasma-shell.xml
protocols/plasma-virtual-desktop.xml
protocols/plasma-window-management.xml
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn'
'--exclude=.svnignore'
old/plasma-wayland-protocols-1.3.0/src/protocols/contrast.xml
new/plasma-wayland-protocols-1.4.0/src/protocols/contrast.xml
--- old/plasma-wayland-protocols-1.3.0/src/protocols/contrast.xml
2021-05-01 02:47:37.000000000 +0200
+++ new/plasma-wayland-protocols-1.4.0/src/protocols/contrast.xml
2021-09-05 02:04:39.000000000 +0200
@@ -6,7 +6,7 @@
SPDX-License-Identifier: LGPL-2.1-or-later
]]></copyright>
- <interface name="org_kde_kwin_contrast_manager" version="1">
+ <interface name="org_kde_kwin_contrast_manager" version="2">
<request name="create">
<arg name="id" type="new_id" interface="org_kde_kwin_contrast"/>
<arg name="surface" type="object" interface="wl_surface"/>
@@ -15,7 +15,7 @@
<arg name="surface" type="object" interface="wl_surface"/>
</request>
</interface>
- <interface name="org_kde_kwin_contrast" version="1">
+ <interface name="org_kde_kwin_contrast" version="2">
<request name="commit">
</request>
<request name="set_region">
@@ -33,5 +33,26 @@
<request name="release" type="destructor">
<description summary="release the contrast object"/>
</request>
+
+ <request name="set_frost" since="2">
+ <description summary="opt into frost effect w/ given colour">
+ enables 'frost' variant of contrast effect.
+
+ 'frost' is an enhanced version of the contrast effect that
+ uses different colour arithmetic to get backgrounds simultaneously
+ higher in contrast and (apparent) transparency.
+
+ r, g, b, a are channels from 0-255, indicating a colour to use in
contrast calculation.
+ should be based off of the "main" background colour of the surface.
+ </description>
+
+ <arg name="red" type="int" />
+ <arg name="green" type="int" />
+ <arg name="blue" type="int" />
+ <arg name="alpha" type="int" />
+ </request>
+ <request name="unset_frost" since="2">
+ <description summary="opts out of frost effect" />
+ </request>
</interface>
</protocol>
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn'
'--exclude=.svnignore'
old/plasma-wayland-protocols-1.3.0/src/protocols/fake-input.xml
new/plasma-wayland-protocols-1.4.0/src/protocols/fake-input.xml
--- old/plasma-wayland-protocols-1.3.0/src/protocols/fake-input.xml
2021-05-01 02:47:37.000000000 +0200
+++ new/plasma-wayland-protocols-1.4.0/src/protocols/fake-input.xml
2021-09-05 02:04:39.000000000 +0200
@@ -41,7 +41,7 @@
<request name="touch_down" since="2">
<description summary="touch down event">
A client should use this request to send touch down event at
specific
- co-ordinates.
+ coordinates.
</description>
<arg name="id" type="uint" summary="unique id for touch down event"/>
<arg name="x" type="fixed" summary="x coordinate for touch down
event"/>
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn'
'--exclude=.svnignore'
old/plasma-wayland-protocols-1.3.0/src/protocols/fullscreen-shell.xml
new/plasma-wayland-protocols-1.4.0/src/protocols/fullscreen-shell.xml
--- old/plasma-wayland-protocols-1.3.0/src/protocols/fullscreen-shell.xml
2021-05-01 02:47:37.000000000 +0200
+++ new/plasma-wayland-protocols-1.4.0/src/protocols/fullscreen-shell.xml
2021-09-05 02:04:39.000000000 +0200
@@ -72,11 +72,11 @@
When the wl_fullscreen_shell interface is bound, this event is emitted
once for each capability advertised. Valid capabilities are given by
the wl_fullscreen_shell.capability enum. If clients want to take
- advantage of any of these capabilities, they sould use a
+ advantage of any of these capabilities, they should use a
wl_display.sync request immediately after binding to ensure that they
receive all the capability events.
</description>
- <arg name="capabilty" type="uint"/>
+ <arg name="capability" type="uint"/>
</event>
<enum name="present_method">
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn'
'--exclude=.svnignore'
old/plasma-wayland-protocols-1.3.0/src/protocols/kde-output-device-v2.xml
new/plasma-wayland-protocols-1.4.0/src/protocols/kde-output-device-v2.xml
--- old/plasma-wayland-protocols-1.3.0/src/protocols/kde-output-device-v2.xml
1970-01-01 01:00:00.000000000 +0100
+++ new/plasma-wayland-protocols-1.4.0/src/protocols/kde-output-device-v2.xml
2021-09-05 02:04:39.000000000 +0200
@@ -0,0 +1,318 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<protocol name="kde_output_device_v2">
+ <copyright><![CDATA[
+ SPDX-FileCopyrightText: 2008-2011 Kristian H??gsberg
+ SPDX-FileCopyrightText: 2010-2011 Intel Corporation
+ SPDX-FileCopyrightText: 2012-2013 Collabora, Ltd.
+ SPDX-FileCopyrightText: 2015 Sebastian K??gler <se...@kde.org>
+ SPDX-FileCopyrightText: 2021 M??ven Car <meven....@enioka.com>
+
+ SPDX-License-Identifier: MIT-CMU
+ ]]></copyright>
+
+
+ <interface name="kde_output_device_v2" version="1">
+ <description summary="output configuration representation">
+ An output device describes a display device available to the compositor.
+ output_device is similar to wl_output, but focuses on output
+ configuration management.
+
+ A client can query all global output_device objects to enlist all
+ available display devices, even those that may currently not be
+ represented by the compositor as a wl_output.
+
+ The client sends configuration changes to the server through the
+ outputconfiguration interface, and the server applies the configuration
+ changes to the hardware and signals changes to the output devices
+ accordingly.
+
+ This object is published as global during start up for every available
+ display devices, or when one later becomes available, for example by
+ being hotplugged via a physical connector.
+ </description>
+
+ <enum name="subpixel">
+ <description summary="subpixel geometry information">
+ This enumeration describes how the physical pixels on an output are
+ laid out.
+ </description>
+ <entry name="unknown" value="0"/>
+ <entry name="none" value="1"/>
+ <entry name="horizontal_rgb" value="2"/>
+ <entry name="horizontal_bgr" value="3"/>
+ <entry name="vertical_rgb" value="4"/>
+ <entry name="vertical_bgr" value="5"/>
+ </enum>
+
+ <enum name="transform">
+ <description summary="transform from framebuffer to output">
+ This describes the transform, that a compositor will apply to a
+ surface to compensate for the rotation or mirroring of an
+ output device.
+
+ The flipped values correspond to an initial flip around a
+ vertical axis followed by rotation.
+
+ The purpose is mainly to allow clients to render accordingly and
+ tell the compositor, so that for fullscreen surfaces, the
+ compositor is still able to scan out directly client surfaces.
+ </description>
+
+ <entry name="normal" value="0"/>
+ <entry name="90" value="1"/>
+ <entry name="180" value="2"/>
+ <entry name="270" value="3"/>
+ <entry name="flipped" value="4"/>
+ <entry name="flipped_90" value="5"/>
+ <entry name="flipped_180" value="6"/>
+ <entry name="flipped_270" value="7"/>
+ </enum>
+
+ <event name="geometry">
+ <description summary="geometric properties of the output">
+ The geometry event describes geometric properties of the output.
+ The event is sent when binding to the output object and whenever
+ any of the properties change.
+ </description>
+ <arg name="x" type="int"
+ summary="x position within the global compositor space"/>
+ <arg name="y" type="int"
+ summary="y position within the global compositor space"/>
+ <arg name="physical_width" type="int"
+ summary="width in millimeters of the output"/>
+ <arg name="physical_height" type="int"
+ summary="height in millimeters of the output"/>
+ <arg name="subpixel" type="int"
+ summary="subpixel orientation of the output"/>
+ <arg name="make" type="string"
+ summary="textual description of the manufacturer"/>
+ <arg name="model" type="string"
+ summary="textual description of the model"/>
+ <arg name="transform" type="int"
+ summary="transform that maps framebuffer to output"/>
+ </event>
+
+ <event name="current_mode">
+ <description summary="current mode">
+ This event describes the mode currently in use for this head. It is
only
+ sent if the output is enabled.
+ </description>
+ <arg name="mode" type="object" interface="kde_output_device_mode_v2"/>
+ </event>
+
+ <event name="mode">
+ <description summary="advertise available output modes and current one">
+ The mode event describes an available mode for the output.
+
+ When the client binds to the output_device object, the server sends
this
+ event once for every available mode the output_device can be operated
by.
+
+ There will always be at least one event sent out on initial binding,
+ which represents the current mode.
+
+ Later if an output changes, its mode event is sent again for the
+ eventual added modes and lastly the current mode. In other words, the
+ current mode is always represented by the latest event sent with the
current
+ flag set.
+
+ The size of a mode is given in physical hardware units of the output
device.
+ This is not necessarily the same as the output size in the global
compositor
+ space. For instance, the output may be scaled, as described in
+ kde_output_device_v2.scale, or transformed, as described in
+ kde_output_device_v2.transform.
+ </description>
+ <arg name="mode" type="new_id" interface="kde_output_device_mode_v2"/>
+ </event>
+
+ <event name="done">
+ <description summary="sent all information about output">
+ This event is sent after all other properties have been
+ sent on binding to the output object as well as after any
+ other output property change have been applied later on.
+ This allows to see changes to the output properties as atomic,
+ even if multiple events successively announce them.
+ </description>
+ </event>
+
+ <event name="scale">
+ <description summary="output scaling properties">
+ This event contains scaling geometry information
+ that is not in the geometry event. It may be sent after
+ binding the output object or if the output scale changes
+ later. If it is not sent, the client should assume a
+ scale of 1.
+
+ A scale larger than 1 means that the compositor will
+ automatically scale surface buffers by this amount
+ when rendering. This is used for high resolution
+ displays where applications rendering at the native
+ resolution would be too small to be legible.
+
+ It is intended that scaling aware clients track the
+ current output of a surface, and if it is on a scaled
+ output it should use wl_surface.set_buffer_scale with
+ the scale of the output. That way the compositor can
+ avoid scaling the surface, and the client can supply
+ a higher detail image.
+ </description>
+ <arg name="factor" type="fixed" summary="scaling factor of output"/>
+ </event>
+
+ <event name="edid">
+ <description summary="advertise EDID data for the output">
+ The edid event encapsulates the EDID data for the outputdevice.
+
+ The event is sent when binding to the output object. The EDID
+ data may be empty, in which case this event is sent anyway.
+ If the EDID information is empty, you can fall back to the name
+ et al. properties of the outputdevice.
+ </description>
+ <arg name="raw" type="string" summary="base64-encoded EDID string"/>
+ </event>
+
+ <event name="enabled">
+ <description summary="output is enabled or disabled">
+ The enabled event notifies whether this output is currently
+ enabled and used for displaying content by the server.
+ The event is sent when binding to the output object and
+ whenever later on an output changes its state by becoming
+ enabled or disabled.
+ </description>
+ <arg name="enabled" type="int" summary="output enabled state"/>
+ </event>
+
+ <event name="uuid">
+ <description summary="A unique id for this outputdevice">
+ The uuid can be used to identify the output. It's controlled by
+ the server entirely. The server should make sure the uuid is
+ persistent across restarts. An empty uuid is considered invalid.
+ </description>
+ <arg name="uuid" type="string" summary="output devices ID"/>
+ </event>
+
+ <event name="serial_number">
+ <description summary="Serial Number">
+ Serial ID of the monitor, sent on startup before the first done event.
+ </description>
+ <arg name="serialNumber" type="string"
+ summary="textual representation of serial number"/>
+ </event>
+ <event name="eisa_id">
+ <description summary="EISA ID">
+ EISA ID of the monitor, sent on startup before the first done event.
+ </description>
+ <arg name="eisaId" type="string"
+ summary="textual representation of EISA identifier"/>
+ </event>
+
+ <enum name="capability" bitfield="true">
+ <description summary="describes capabilities of the outputdevice">
+ Describes what capabilities this device has.
+ </description>
+ <entry name="overscan" value="1"
+ summary="if this output_device can use overscan"/>
+ <entry name="vrr" value="2"
+ summary="if this outputdevice supports variable refresh rate"/>
+ <entry name="rgb_range" value="4"
+ summary="if setting the rgb range is possible"/>
+ </enum>
+
+ <event name="capabilities">
+ <description summary="capability flags">
+ What capabilities this device has, sent on startup before the first
+ done event.
+ </description>
+ <arg name="flags" type="uint" enum="capability"/>
+ </event>
+
+ <event name="overscan">
+ <description summary="overscan">
+ Overscan value of the monitor in percent, sent on startup before the
+ first done event.
+ </description>
+ <arg name="overscan" type="uint"
+ summary="amount of overscan of the monitor"/>
+ </event>
+
+ <enum name="vrr_policy">
+ <description summary="describes vrr policy">
+ Describes when the compositor may employ variable refresh rate
+ </description>
+ <entry name="never" value="0"/>
+ <entry name="always" value="1"/>
+ <entry name="automatic" value="2"/>
+ </enum>
+
+ <event name="vrr_policy">
+ <description summary="Variable Refresh Rate Policy">
+ What policy the compositor will employ regarding its use of variable
+ refresh rate.
+ </description>
+ <arg name="vrr_policy" type="uint" enum="vrr_policy"/>
+ </event>
+
+ <enum name="rgb_range">
+ <description summary="describes RGB range policy">
+ Whether full or limited color range should be used
+ </description>
+ <entry name="automatic" value="0"/>
+ <entry name="full" value="1"/>
+ <entry name="limited" value="2"/>
+ </enum>
+
+ <event name="rgb_range">
+ <description summary="RGB range">
+ What rgb range the compositor is using for this output
+ </description>
+ <arg name="rgb_range" type="uint" enum="rgb_range"/>
+ </event>
+
+ </interface>
+
+ <interface name="kde_output_device_mode_v2" version="1">
+ <description summary="output mode">
+ This object describes an output mode.
+
+ Some heads don't support output modes, in which case modes won't be
+ advertised.
+
+ Properties sent via this interface are applied atomically via the
+ kde_output_device.done event. No guarantees are made regarding the order
+ in which properties are sent.
+ </description>
+
+ <event name="size">
+ <description summary="mode size">
+ This event describes the mode size. The size is given in physical
+ hardware units of the output device. This is not necessarily the same
as
+ the output size in the global compositor space. For instance, the
output
+ may be scaled or transformed.
+ </description>
+ <arg name="width" type="int" summary="width of the mode in hardware
units"/>
+ <arg name="height" type="int" summary="height of the mode in hardware
units"/>
+ </event>
+
+ <event name="refresh">
+ <description summary="mode refresh rate">
+ This event describes the mode's fixed vertical refresh rate. It is only
+ sent if the mode has a fixed refresh rate.
+ </description>
+ <arg name="refresh" type="int" summary="vertical refresh rate in mHz"/>
+ </event>
+
+ <event name="preferred">
+ <description summary="mode is preferred">
+ This event advertises this mode as preferred.
+ </description>
+ </event>
+
+ <event name="removed">
+ <description summary="the mode has been destroyed">
+ The compositor will destroy the object immediately after sending this
+ event, so it will become invalid and the client should release any
+ resources associated with it.
+ </description>
+ </event>
+ </interface>
+
+</protocol>
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn'
'--exclude=.svnignore'
old/plasma-wayland-protocols-1.3.0/src/protocols/kde-output-management-v2.xml
new/plasma-wayland-protocols-1.4.0/src/protocols/kde-output-management-v2.xml
---
old/plasma-wayland-protocols-1.3.0/src/protocols/kde-output-management-v2.xml
1970-01-01 01:00:00.000000000 +0100
+++
new/plasma-wayland-protocols-1.4.0/src/protocols/kde-output-management-v2.xml
2021-09-05 02:04:39.000000000 +0200
@@ -0,0 +1,197 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<protocol name="kde_output_management_v2">
+ <copyright><![CDATA[
+ SPDX-FileCopyrightText: 2008-2011 Kristian H??gsberg
+ SPDX-FileCopyrightText: 2010-2011 Intel Corporation
+ SPDX-FileCopyrightText: 2012-2013 Collabora, Ltd.
+ SPDX-FileCopyrightText: 2015 Sebastian K??gler <se...@kde.org>
+ SPDX-FileCopyrightText: 2021 M??ven Car <meven....@enioka.com>
+
+ SPDX-License-Identifier: MIT-CMU
+ ]]></copyright>
+
+<interface name="kde_output_management_v2" version="1">
+ <description summary="configuration of server outputs through clients">
+ This interface enables clients to set properties of output devices for
screen
+ configuration purposes via the server. To this end output devices are
referenced
+ by global kde_output_device_v2 objects.
+
+ outputmanagement (wl_global)
+ --------------------------
+ request:
+ * create_configuration -> outputconfiguration (wl_resource)
+
+ outputconfiguration (wl_resource)
+ --------------------------
+ requests:
+ * enable(outputdevice, bool)
+ * mode(outputdevice, mode)
+ * transformation(outputdevice, flag)
+ * position(outputdevice, x, y)
+ * apply
+
+ events:
+ * applied
+ * failed
+
+ The server registers one outputmanagement object as a global object. In
order
+ to configure outputs a client requests create_configuration, which
provides a
+ resource referencing an outputconfiguration for one-time configuration.
That
+ way the server knows which requests belong together and can group them by
that.
+
+ On the outputconfiguration object the client calls for each output whether
the
+ output should be enabled, which mode should be set (by referencing the
mode from
+ the list of announced modes) and the output's global position. Once all
outputs
+ are configured that way, the client calls apply.
+ At that point and not earlier the server should try to apply the
configuration.
+ If this succeeds the server emits the applied signal, otherwise the failed
+ signal, such that the configuring client is noticed about the success of
its
+ configuration request.
+
+ Through this design the interface enables atomic output configuration
changes if
+ internally supported by the server.
+
+ </description>
+ <request name="create_configuration">
+ <description summary="provide outputconfiguration object for configuring
outputs">
+ Request an outputconfiguration object through which the client can
configure
+ output devices.
+ </description>
+ <arg name="id" type="new_id" interface="kde_output_configuration_v2"/>
+ </request>
+
+</interface>
+
+<interface name="kde_output_configuration_v2" version="1">
+ <description summary="configure single output devices">
+ outputconfiguration is a client-specific resource that can be used to ask
+ the server to apply changes to available output devices.
+
+ The client receives a list of output devices from the registry. When it
wants
+ to apply new settings, it creates a configuration object from the
+ outputmanagement global, writes changes through this object's enable,
scale,
+ transform and mode calls. It then asks the server to apply these settings
in
+ an atomic fashion, for example through Linux' DRM interface.
+
+ The server signals back whether the new settings have applied successfully
+ or failed to apply. outputdevice objects are updated after the changes
have been
+ applied to the hardware and before the server side sends the applied event.
+ </description>
+
+ <request name="enable">
+ <description summary="enable or disable an output">
+ Mark the output as enabled or disabled.
+ </description>
+ <arg name="outputdevice" type="object" interface="kde_output_device_v2"
summary="outputdevice to be en- or disabled"/>
+ <arg name="enable" type="int" summary="1 to enable or 0 to disable this
output"/>
+ </request>
+
+ <request name="mode">
+ <description summary="switch output-device to mode">
+ Sets the mode for a given output.
+ </description>
+ <arg name="outputdevice" type="object" interface="kde_output_device_v2"
summary="outputdevice this mode change applies to"/>
+ <arg name="mode" type="object" interface="kde_output_device_mode_v2"
summary="the mode to apply"/>
+ </request>
+
+ <request name="transform">
+ <description summary="transform output-device">
+ Sets the transformation for a given output.
+ </description>
+ <arg name="outputdevice" type="object" interface="kde_output_device_v2"
summary="outputdevice this transformation change applies to"/>
+ <arg name="transform" type="int" summary="transform enum"/>
+ </request>
+
+ <request name="position">
+ <description summary="position output in global space">
+ Sets the position for this output device. (x,y) describe the top-left
corner
+ of the output in global space, whereby the origin (0,0) of the global
space
+ has to be aligned with the top-left corner of the most left and in case
this
+ does not define a single one the top output.
+
+ There may be no gaps or overlaps between outputs, i.e. the outputs are
+ stacked horizontally, vertically, or both on each other.
+ </description>
+ <arg name="outputdevice" type="object" interface="kde_output_device_v2"
summary="outputdevice this position applies to"/>
+ <arg name="x" type="int" summary="position on the x-axis"/>
+ <arg name="y" type="int" summary="position on the y-axis"/>
+ </request>
+
+ <request name="scale">
+ <description summary="set scaling factor of this output">
+ Sets the scaling factor for this output device.
+ </description>
+ <arg name="outputdevice" type="object" interface="kde_output_device_v2"
summary="outputdevice this scale change applies to"/>
+ <arg name="scale" type="fixed" summary="scaling factor"/>
+ </request>
+
+ <request name="apply">
+ <description summary="apply configuration changes to all output devices">
+ Asks the server to apply property changes requested through this
outputconfiguration
+ object to all outputs on the server side.
+ </description>
+ </request>
+
+ <event name="applied">
+ <description summary="configuration changes have been applied">
+ Sent after the server has successfully applied the changes.
+ .
+ </description>
+ </event>
+
+ <event name="failed">
+ <description summary="configuration changes failed to apply">
+ Sent if the server rejects the changes or failed to apply them.
+ </description>
+ </event>
+
+ <request name="destroy" type="destructor">
+ <description summary="release the outputconfiguration object"/>
+ </request>
+
+ <request name="overscan">
+ <description summary="set overscan value">
+ Set the overscan value of this output device with a value in percent.
+ </description>
+ <arg name="outputdevice" type="object" interface="kde_output_device_v2"
summary="outputdevice overscan applies to"/>
+ <arg name="overscan" type="uint" summary="overscan value"/>
+ </request>
+
+ <enum name="vrr_policy">
+ <description summary="describes vrr policy">
+ Describes when the compositor may employ variable refresh rate
+ </description>
+ <entry name="never" value="0"/>
+ <entry name="always" value="1"/>
+ <entry name="automatic" value="2"/>
+ </enum>
+
+ <request name="set_vrr_policy">
+ <description summary="set the VRR policy">
+ Set what policy the compositor should employ regarding its use of
+ variable refresh rate.
+ </description>
+ <arg name="outputdevice" type="object" interface="kde_output_device_v2"
summary="outputdevice this VRR policy applies to"/>
+ <arg name="policy" type="uint" enum="vrr_policy" summary="the vrr policy
to apply"/>
+ </request>
+
+ <enum name="rgb_range">
+ <description summary="describes RGB range policy">
+ Whether this output should use full or limited rgb.
+ </description>
+ <entry name="automatic" value="0"/>
+ <entry name="full" value="1"/>
+ <entry name="limited" value="2"/>
+ </enum>
+
+ <request name="set_rgb_range">
+ <description summary="RGB range">
+ Whether full or limited color range should be used
+ </description>
+ <arg name="outputdevice" type="object" interface="kde_output_device_v2"
summary="outputdevice the rgb range applies to"/>
+ <arg name="rgb_range" type="uint" enum="rgb_range"/>
+ </request>
+
+</interface>
+
+</protocol>
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn'
'--exclude=.svnignore'
old/plasma-wayland-protocols-1.3.0/src/protocols/plasma-window-management.xml
new/plasma-wayland-protocols-1.4.0/src/protocols/plasma-window-management.xml
---
old/plasma-wayland-protocols-1.3.0/src/protocols/plasma-window-management.xml
2021-05-01 02:47:37.000000000 +0200
+++
new/plasma-wayland-protocols-1.4.0/src/protocols/plasma-window-management.xml
2021-09-05 02:04:39.000000000 +0200
@@ -6,7 +6,7 @@
SPDX-License-Identifier: LGPL-2.1-or-later
]]></copyright>
- <interface name="org_kde_plasma_window_management" version="14">
+ <interface name="org_kde_plasma_window_management" version="15">
<description summary="application windows management">
This interface manages application windows.
It provides requests to show and hide the desktop and emits
@@ -101,7 +101,7 @@
</event>
</interface>
- <interface name="org_kde_plasma_window" version="14">
+ <interface name="org_kde_plasma_window" version="15">
<description summary="interface to control application windows">
Manages and control an application window.
@@ -366,5 +366,52 @@
<arg name="id" type="string" summary="activity id"/>
</event>
+ <request name="send_to_output" since="15">
+ <description summary="send window to specified output">
+ Requests this window to be displayed in a specific output.
+ </description>
+ <arg name="output" type="object" interface="wl_output"/>
+ </request>
+ </interface>
+
+ <interface name="org_kde_plasma_activation_feedback" version="1">
+ <description summary="activation feedback">
+ The activation manager interface provides a way to get notified
+ when an application is about to be activated.
+ </description>
+
+ <request name="destroy" type="destructor">
+ <description summary="destroy the activation manager object">
+ Destroy the activation manager object. The activation objects
introduced
+ by this manager object will be unaffected.
+ </description>
+ </request>
+
+ <event name="activation">
+ <description summary="notify that an app is starting">
+ Will be issued when an app is set to be activated. It offers
+ an instance of org_kde_plasma_activation that will tell us the app_id
+ and the extent of the activation.
+ </description>
+ <arg name="id" type="new_id" interface="org_kde_plasma_activation"/>
+ </event>
+ </interface>
+
+ <interface name="org_kde_plasma_activation" version="1">
+ <request name="destroy" type="destructor">
+ <description summary="destroy the org_kde_plasma_activation object">
+ Notify the compositor that the org_kde_plasma_activation object will no
+ longer be used.
+ </description>
+ </request>
+
+ <event name="app_id">
+ <description summary="Offers the app_id"></description>
+ <arg name="app_id" type="string" summary="application id, as described
in xdg_activation_v1"/>
+ </event>
+
+ <event name="finished">
+ <description summary="Notifies about activation finished, either by
activation or because it got invalidated"></description>
+ </event>
</interface>
</protocol>
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn'
'--exclude=.svnignore'
old/plasma-wayland-protocols-1.3.0/src/protocols/text-input-unstable-v2.xml
new/plasma-wayland-protocols-1.4.0/src/protocols/text-input-unstable-v2.xml
--- old/plasma-wayland-protocols-1.3.0/src/protocols/text-input-unstable-v2.xml
2021-05-01 02:47:37.000000000 +0200
+++ new/plasma-wayland-protocols-1.4.0/src/protocols/text-input-unstable-v2.xml
2021-09-05 02:04:39.000000000 +0200
@@ -238,7 +238,7 @@
The leave notification is sent before the enter notification
for the new focus.
- When the seat has the keyboard capabillity the text-input focus follows
+ When the seat has the keyboard capability the text-input focus follows
the keyboard focus.
</description>
<arg name="serial" type="uint"/>
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn'
'--exclude=.svnignore'
old/plasma-wayland-protocols-1.3.0/src/protocols/text-input.xml
new/plasma-wayland-protocols-1.4.0/src/protocols/text-input.xml
--- old/plasma-wayland-protocols-1.3.0/src/protocols/text-input.xml
2021-05-01 02:47:37.000000000 +0200
+++ new/plasma-wayland-protocols-1.4.0/src/protocols/text-input.xml
2021-09-05 02:04:39.000000000 +0200
@@ -195,7 +195,7 @@
(for example on unfocus).
The text input should also handle all preedit_style and preedit_cursor
- events occuring directly before preedit_string.
+ events occurring directly before preedit_string.
</description>
<arg name="serial" type="uint" summary="serial of the latest known text
input state"/>
<arg name="text" type="string"/>
