>-Original Message-
>From: Pekka Paalanen [mailto:ppaala...@gmail.com]
>Sent: Thursday, March 27, 2014 9:06 PM
>To: Jasper St. Pierre
>Cc: Wang, Quanxian; wayland-devel@lists.freedesktop.org
>Subject: Re: weston: weston randr protocol for testing and configuration
>
>Cc: wayland-devel@lists.freedesktop.org
>Subject: Re: weston: weston randr protocol for testing and configuration
>
>On Thu, 27 Mar 2014 04:08:15 +
>"Wang, Quanxian" wrote:
>
>> Hi, Pq
>>
>> The information to identify the unique mode: width, height an
I mean, I'm mostly talking about user configuration in the case of a
desktop, when the user wants to change the mode of the display.
Obviously, it would be best if we could detect hardware edge cases like
that where it's going on the fritz and showing a green tint automatically,
and simply not off
On Thu, 27 Mar 2014 08:31:34 -0400
"Jasper St. Pierre" wrote:
> I don't think the user really knows what refresh is either.
>
> I'm actually curious: is there a reason to ever expose different modes to
> the user that have the same width/height but different timings? What's the
> rationale for c
I don't think the user really knows what refresh is either.
I'm actually curious: is there a reason to ever expose different modes to
the user that have the same width/height but different timings? What's the
rationale for choosing one instead of the other? I know nothing about
display panels, kee
On Thu, 27 Mar 2014 04:08:15 +
"Wang, Quanxian" wrote:
> Hi, Pq
>
> The information to identify the unique mode: width, height and refresh are
> enough? Not enough in theory. But is enough in real world. I have checked
> with xrandr. Read the following comment.
>
> Welcome any comment for
Hi, Pq
The information to identify the unique mode: width, height and refresh are
enough? Not enough in theory. But is enough in real world. I have checked with
xrandr. Read the following comment.
Welcome any comment for that.
Thanks
>> +
>> +
>> +
>> +Set the mode of output.
>
There certainly should be no need to worry about multiple threads from
the same client. I think you can work on the assumption that the
programmer who wrote the client is not insane! This is the way commit
for wl_surface works, right?
The per-client pending mode is probably cleanest, but I sus
Original Message-
> > >From: wayland-devel [mailto:wayland-devel-boun...@lists.freedesktop.org]
> On
> > >Behalf Of Pekka Paalanen
> > >Sent: Wednesday, March 26, 2014 3:54 PM
> > >To: Wang, Quanxian
> > >Cc: wayland-devel@lists.freedesktop.org
>
PM
> >To: Wang, Quanxian
> >Cc: wayland-devel@lists.freedesktop.org
> >Subject: Re: weston: weston randr protocol for testing and configuration
> >
> >On Wed, 26 Mar 2014 06:47:50 +
> >"Wang, Quanxian" wrote:
> >
> >> Hi, Pq
> >>
t;> >-Original Message-
>> >From: Pekka Paalanen [mailto:ppaala...@gmail.com]
>> >Sent: Saturday, March 22, 2014 8:20 PM
>> >To: Wang, Quanxian
>> >Cc: wayland-devel@lists.freedesktop.org
>> >Subject: Re: weston: weston randr protocol for testin
...@gmail.com]
> >Sent: Saturday, March 22, 2014 8:20 PM
> >To: Wang, Quanxian
> >Cc: wayland-devel@lists.freedesktop.org
> >Subject: Re: weston: weston randr protocol for testing and configuration
> >
> >
> >Talking about threads here is misleading. Such th
ists.freedesktop.org
>Subject: Re: weston: weston randr protocol for testing and configuration
>
>
>Talking about threads here is misleading. Such threaded operations do not make
>sense to begin with. The question is more about ambiguity between operations
>and acknowledgements, and p
March 22, 2014 8:20 PM
>To: Wang, Quanxian
>Cc: wayland-devel@lists.freedesktop.org
>Subject: Re: weston: weston randr protocol for testing and configuration
>
>Hi
>
>On Fri, 14 Mar 2014 11:18:48 +0800
>Quanxian Wang wrote:
>
>> Objective:
>> With discussion in
Hi
On Fri, 14 Mar 2014 11:18:48 +0800
Quanxian Wang wrote:
> Objective:
> With discussion in mail list, currently we have an agreement. Randr
> interfaces will not be exposed public.
> The objective will be only for testing and configuration. Thanks Pq, Jason,
> Jasper, Hardening, and other's
Objective:
With discussion in mail list, currently we have an agreement. Randr interfaces
will not be exposed public.
The objective will be only for testing and configuration. Thanks Pq, Jason,
Jasper, Hardening, and other's comment.
Before sending the email, the function list below is implement
16 matches
Mail list logo
