[PATCHv2] Add name event to xdg-output
ppaalanen at gmail.com
Mon Apr 9 08:09:59 UTC 2018
On Sun, 8 Apr 2018 10:25:21 -0400
Drew DeVault <sir at cmpwn.com> wrote:
> Signed-off-by: Drew DeVault <sir at cmpwn.com>
> Reviewed-by: Simon Ser <contact at emersion.fr>
> Thanks Daniel for pointing out my silly mistakes
> unstable/xdg-output/xdg-output-unstable-v1.xml | 14 +++++++++++++-
> 1 file changed, 13 insertions(+), 1 deletion(-)
> diff --git a/unstable/xdg-output/xdg-output-unstable-v1.xml b/unstable/xdg-output/xdg-output-unstable-v1.xml
> index 0c0c481..e6ad6fe 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,17 @@
> + <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 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>
the naming has been discussed before, below I'm listing some of the
questions that arose back then that I can remember.
Does this name correspond to the physical connector or to the specific
monitor connected? Or some abstract "output" concept, see the next
paragraph about clone mode.
wl_output is pretty much defined to correspond to a monitor, not a
connector, as it carries things like monitor make and model. When in
clone mode, there will be two or more wl_outputs that are driven
identically by a compositor. How is the xdg_output name affectd by
this? Would xdg_outputs for the cloned wl_outputs report identical
names to signify they in fact always show the exact same image?
Is this name intended to be stable and persistent, so that applications
can expect to save it in a config and find the same one later, after a
machine reboot, at least if the configuration of that output has not
changed and the compositor is still the same version?
The name is arbitrary, right? No standardization is inteneded? I.e.
switching compositors will likely result in different names.
Is the name enough, would you perhaps want to have a human-readable
description string as well? Perhaps something for a user to totally
customize and more verbose than just a name?
I think it would be good to explicitly answer most of these questions
in the spec, even if "configured by name" does imply some answers.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 833 bytes
Desc: OpenPGP digital signature
More information about the wayland-devel