[PATCH 1/6] Add weston randr protocol
quanxian.wang at intel.com
Thu Mar 13 19:33:52 PDT 2014
From: magcius at gmail.com [mailto:magcius at gmail.com] On Behalf Of Jasper St. Pierre
Sent: Monday, March 10, 2014 10:42 AM
To: Wang, Quanxian
Cc: Hardening; wayland-devel at lists.freedesktop.org; Zhang, Xiong Y; Pekka Paalanen; Matthias Clasen; Jason Ekstrand
Subject: Re: [PATCH 1/6] Add weston randr protocol
There's two different things here. There's the protocol and the "UI". (By UI I also mean a command-line tool like /usr/bin/xrandr, I just mean the way the user does a mode-set).
I think to build a good UI, we need a list of available modes that the user can choose from. Having a tool where the user enters two numbers, and then tells the user "No, guess again" if they entered the wrong numbers is bad user interface design.
But, as Hardening said, the protocol should allow setting modes that aren't in the advertised list.
[Wang, Quanxian] Sorry for response later. From command line tools, Weston-wrandr will provide the mode list instead of guessing what is in. you can firstly use 'weston-wrandr --output' to query all modes of output. And then select one of them.
Of course, if you want to new a mode, that is fine. It is also reasonable for me.
On Sun, Mar 9, 2014 at 10:34 PM, Wang, Quanxian <quanxian.wang at intel.com<mailto:quanxian.wang at intel.com>> wrote:
>> 5) mode setting parameters control
>> Mode and output will be under the control. User could not randomly to set their
>mode. They have to select the available modes and outputs provided by
>compositor. Don't allow random mode setting. The mode and output information
>could be provided by weston-randr apps or wl_output interface.
>I don't think that allowing to set only announced modes is a good idea.
>The RDP compositor is a good example where you can't know the supported
>modes (as nearly all modes can be supported).
>IIRC depending on the drivers, drm can also set arbitrary modes.
[Wang, Quanxian] so, let user set the mode without limitation? Not sure if we should support that.
Any comment for this requirement?
wayland-devel mailing list
wayland-devel at lists.freedesktop.org<mailto:wayland-devel at lists.freedesktop.org>
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the wayland-devel