[PATCHv3] Add name event to xdg-output
pkerling at casix.org
Wed Apr 11 07:17:19 UTC 2018
maybe I missed it at some point in the discussion (sorry if that is the
case), but what is your use case for the "name?" What are clients
expected to use it for?
The description mentions "similar behaviors", but it is unclear to me
what you are referring to.
2018-04-10 (火) の 20:27 -0400 に Drew DeVault さんは書きました:
> Signed-off-by: Drew DeVault <sir at cmpwn.com>
> Reviewed-by: Simon Ser <contact at emersion.fr>
> This version clarifies the uniqueness constraint, mapping of names to
> wl_outputs, and persistence between sessions.
> .../xdg-output/xdg-output-unstable-v1.xml | 19
> 1 file changed, 18 insertions(+), 1 deletion(-)
> diff --git a/unstable/xdg-output/xdg-output-unstable-v1.xml
> index 0c0c481..b46c9df 100644
> --- a/unstable/xdg-output/xdg-output-unstable-v1.xml
> +++ b/unstable/xdg-output/xdg-output-unstable-v1.xml
> @@ -77,7 +77,7 @@
> - <interface name="zxdg_output_v1" version="1">
> + <interface name="zxdg_output_v1" version="2">
> <description summary="compositor logical output region">
> An xdg_output describes part of the compositor geometry.
> @@ -157,5 +157,22 @@
> + <event name="name" since="2">
> + <description summary="name of this output">
> + Many compositors will assign names to their outputs, show them
> to the user,
> + allow them to be configured by name, etc. The client may wish to
> know this
> + name as well to offer the user similar behaviors.
> + The naming convention is compositor defined. Each name is unique
> among all
> + wl_output globals, but if a wl_output global is destroyed the
> same name may
> + be reused later. The names will also remain consistent across
> sessions with
> + the same hardware and software configuration.
> + The name event is sent after creating an xdg_output (see
> + xdg_output_manager.get_xdg_output).
> + </description>
> + <arg name="name" type="string" summary="output name"/>
> + </event>
More information about the wayland-devel