Re: [PATCH wayland-protocols v7] Add zwp_linux_explicit_synchronization_v1

2018-11-27 Thread Alexandros Frantzis
On Tue, Nov 27, 2018 at 05:17:40PM +0200, Alexandros Frantzis wrote: > On Tue, Nov 27, 2018 at 10:53:45AM +0200, Pekka Paalanen wrote: > > Yes, we probably should have some wording that if a client is letting > > something like EGL to commit the buffers, it must not attempt to use > > the fence

Re: [PATCH wayland-protocols v7] Add zwp_linux_explicit_synchronization_v1

2018-11-27 Thread Alexandros Frantzis
On Tue, Nov 27, 2018 at 10:53:45AM +0200, Pekka Paalanen wrote: > Yes, we probably should have some wording that if a client is letting > something like EGL to commit the buffers, it must not attempt to use > the fence extension on that wl_surface itself because EGL will probably > be using the

RE: Re: [PATCH] wayland-server: update the client fd when it failed to flush with EAGAIN

2018-11-27 Thread 박성진
> On Tue, 27 Nov 2018 17:59:16 +0900> 박성진 wrote:> > Hi Derek>> On 11/22/18 11:08 PM, Jeonghyun Kang wrote:> > > What if it's a frame event that gets dropped and not an input event?  Or> > > a resource destroy?> > Instead of destroying a connection, destroying a resource seems to be more> >

Re: Best way to achieve very slow pointer motion? (for accessibility)

2018-11-27 Thread Peter Hutterer
On Tue, Nov 27, 2018 at 11:25:05AM +0100, Colomban Wendling wrote: > Hello, > > I'm working on the MATE desktop environment to try and enhance the > pointer speed user setting to allow for a very slow pointer to better > fit accessibility for people with limited motor abilities (motor >

Re: [PATCH] wayland-server: update the client fd when it failed to flush with EAGAIN

2018-11-27 Thread Pekka Paalanen
On Mon, 26 Nov 2018 11:12:08 -0600 Derek Foreman wrote: > On 11/22/18 11:08 PM, Jeonghyun Kang wrote: > > When a wayland compositor gets an EAGAIN error whenever > > sending or receiving event(s) to a client in the > > wl_closure_send() or the wl_closure_queue(), the error > > variable of the

RE: Re: [PATCH] wayland-server: update the client fd when it failed to flush with EAGAIN

2018-11-27 Thread 박성진
Hi Derek>> On 11/22/18 11:08 PM, Jeonghyun Kang wrote: >> When a wayland compositor gets an EAGAIN error whenever >> sending or receiving event(s) to a client in the >> wl_closure_send() or the wl_closure_queue(), the error >> variable of the wl_client for the client will be set to >>

Re: [PATCH wayland-protocols v7] Add zwp_linux_explicit_synchronization_v1

2018-11-27 Thread Pekka Paalanen
On Mon, 26 Nov 2018 15:14:45 + Tomek Bury wrote: > Hi Pekka, > > Yes, sorry, I was writing specifically about Weston implementation. In the > merge request from Alexandros the actual compatibility check is in the main > compositor, while compositor doesn't have enough information to decide

Best way to achieve very slow pointer motion? (for accessibility)

2018-11-27 Thread Colomban Wendling
Hello, I'm working on the MATE desktop environment to try and enhance the pointer speed user setting to allow for a very slow pointer to better fit accessibility for people with limited motor abilities (motor deficiencies, some elderly, etc.). Currently, MATE is providing a setting controlling

Re: [PATCH wayland-protocols v7] Add zwp_linux_explicit_synchronization_v1

2018-11-27 Thread Tomek Bury
Hi Pekka, > I suppose that applies to the opaque EGL buffers only? Sort of. As far as I understand it, the divide is between wl_surface managed by EGL/WSI vs. wl_surface managed directly by the client application. For EGL case the wl_surface managed by EGL would be set-up more or less like this:

Re: [PATCH] wayland-server: update the client fd when it failed to flush with EAGAIN

2018-11-27 Thread Pekka Paalanen
On Tue, 27 Nov 2018 17:59:16 +0900 박성진 wrote: > Hi Derek>> On 11/22/18 11:08 PM, Jeonghyun Kang wrote: > > What if it's a frame event that gets dropped and not an input event? Or > > a resource destroy? > Instead of destroying a connection, destroying a resource seems to be more > reasonable.