[PATCH 0/3] Add wl_output name event
ppaalanen at gmail.com
Fri Mar 28 06:45:14 PDT 2014
On Wed, 19 Mar 2014 12:01:42 -0500
Jason Ekstrand <jason at jlekstrand.net> wrote:
> I looked over the latest versions, and I think they all look good now from
> a technical perspective. I'm still not 100% sure that this is needed, but
> I think I'm ok with it.
> --Jason Ekstrand
yeah, seems good to me, too. I might like to change the wording
slightly so that the name event is guaranteed to be sent, and not only
"may be sent". I assume it is also supposed to belong to the set of
state that is ended with the 'done' event, I guess that could be more
I imagine this would be useful also, if a client wants to show a menu
with options to maximize or fullscreen onto a specific output. Listing
the outputs by name would let the user know which is which. I guess
presentation applications might like that to put something on the
> On Wed, Mar 19, 2014 at 12:30 AM, Quanxian Wang <quanxian.wang at intel.com>wrote:
> > This event contains a human-readable name of output.
> > It may be sent after binding the output object.
> > It is intended that the client can use this output name
> > as a parameter or display it in logs.
> > For example, in weston randr application, output name can
> > be a parameter in command line to stand for an output.
> > Quanxian Wang (3):
> > wayland: Add wl_output name event
> > shell: Add wl_output name event
> > weston:Add wl_output name event
> > Wayland:
> > protocol/wayland.xml | 12 +++++++++++-
> > 1 file changed, 11 insertions(+), 1 deletion(-)
> > Shell:
> > clients/desktop-shell.c | 12 ++++++++++--
> > clients/window.c | 12 ++++++++++--
> > 2 files changed, 20 insertions(+), 4 deletions(-)
> > Weston:
> > src/compositor.c | 7 +++++--
> > 1 files changed, 5 insertions(+), 2 deletions(-)
> > --
> > 22.214.171.124
More information about the wayland-devel