[ANNOUNCE] libinput 1.11.3

2018-07-24 Thread Peter Hutterer
libinput 1.11.3 is now available. There's only a single change that affects users - the HP Chromebook 14 now has the correct pressure ranges applied. All other changes are merely documentation updates (in case anyone reads the release-specific docs). And the libinput-replay tool was updated to set

Re: [RFC libinput] dox: switch to sphinx for the user-visible documentation

2018-07-24 Thread Peter Hutterer
On Tue, Jul 24, 2018 at 09:27:51AM +0100, Daniel Stone wrote: > Hey, > > On Tue, 24 Jul 2018 at 06:43, Peter Hutterer wrote: > > Sending this out as patch even though what really matters is the > > output. Which is... here, tadaaa! > > > > https://people.freedesktop.org/~whot/libinput-rtd/ > > >

Re: [RFC weston] clients: Don't attach a buffer if mouse cursor surface is unchanged

2018-07-24 Thread Daniel Stone
Hey, On Tue, 24 Jul 2018 at 22:45, Derek Foreman wrote: > On 2018-07-22 05:55 AM, Daniel Stone wrote: > > I take it the problem is that the client sets a particular surface as > > the pointer surface, loses focus, sets the same surface as the pointer > > surface on re-enter after not changing the

Re: [RFC weston] clients: Don't attach a buffer if mouse cursor surface is unchanged

2018-07-24 Thread Derek Foreman
On 2018-07-22 05:55 AM, Daniel Stone wrote: > Hey Derek, > > On Thu, 22 Feb 2018 at 22:16, Derek Foreman wrote: >> Keep track of what cusor image buffer is attached to the cursor >> surface and avoid re-attaching it if we don't have to. >> >> This isn't just an obviously pointless optimization, i

Re: [PATCH weston] simple-dmabuf-drm: use GBM generic calls

2018-07-24 Thread Emil Velikov
Hi everyone, On 11 July 2018 at 09:33, Daniel Stone wrote: > Hi, > On Wed, 11 Jul 2018 at 09:16, Pekka Paalanen wrote: >> On Tue, 10 Jul 2018 17:53:15 +0200 Emilio Pozuelo Monfort >> wrote: >> > No need to write libdrm driver specific code for each supported >> > driver, we can just let GBM ca

Re: [PATCH v4 wayland-protocols] virtual-keyboard: Add new virtual keyboard protocol

2018-07-24 Thread Dorota Czaplejewicz
On Thu, 12 Jul 2018 18:15:32 -0400 Simon Ser wrote: > > Provides the ability to emulate keyboards by applications. Complementary to > > input-method protocol. > > > > The interface is a mirror copy of wl_keyboard, with removed serials, and > > added > > seat binding. > > > > --- > > > > Hello, >

[PATCH v7 wayland-protocols] text-input: Add v3 of the text-input protocol

2018-07-24 Thread Dorota Czaplejewicz
From: Carlos Garnacho This new protocol description is a simplification over v2. - All pre-edit text styling is gone. - Pre-edit cursor can span characters. - No events regarding input panel (OSK) state nor covered rectangle. Compositors are still free to handle situations where the keyboard

Re: [PATCH wayland-protocols] unstable: add xdg-primary-selection protocol

2018-07-24 Thread Simon Ser
Hi Jonas, Any thoughts about this? Thanks, Simon On July 15, 2018 7:36 PM, Simon Ser wrote: > Hi Jonas, > > What do you think of this proposal? (It's basically the GTK protocol with > some prefix changes) > > Thanks, > > Simon > > On July 8, 2018 8:14 PM, Simon Ser wrote: > > This primary se

Re: [PATCH] protocol: allow to send a zero physical output size

2018-07-24 Thread Jonas Ådahl
On Tue, Jul 24, 2018 at 11:44:35AM +0200, Olivier Fourdan wrote: > Hi, > > On Tue, 24 Jul 2018 at 11:34, Simon Ser wrote: > > > > On July 13, 2018 12:00 PM, Daniel Stone wrote: > > > Hi, > > > > > > On Tue, 3 Jul 2018 at 12:27, Simon Ser wrote: > > > > Physical size doesn't always make sense fo

Re: [PATCH] protocol: allow to send a zero physical output size

2018-07-24 Thread Olivier Fourdan
Hi, On Tue, 24 Jul 2018 at 11:34, Simon Ser wrote: > > On July 13, 2018 12:00 PM, Daniel Stone wrote: > > Hi, > > > > On Tue, 3 Jul 2018 at 12:27, Simon Ser wrote: > > > Physical size doesn't always make sense for all outputs. In case > > > it's not available or not relevant, allow compositors

Re: [PATCH] protocol: allow to send a zero physical output size

2018-07-24 Thread Simon Ser
On July 13, 2018 12:00 PM, Daniel Stone wrote: > Hi, > > On Tue, 3 Jul 2018 at 12:27, Simon Ser wrote: > > Physical size doesn't always make sense for all outputs. In case > > it's not available or not relevant, allow compositors to send zero. > > --- > > In practice this doesn't seem to break an

RE: [PATCH v3 weston 4/5] tests: add test for setting gamma

2018-07-24 Thread Harsha Manjula Mallikarjun (RBEI/ECF3)
> -Original Message- > From: Daniel Stone [mailto:dan...@fooishbar.org] > Sent: Saturday, July 21, 2018 5:52 PM > To: Harsha Manjula Mallikarjun (RBEI/ECF3) > > Cc: wayland > Subject: Re: [PATCH v3 weston 4/5] tests: add test for setting gamma > > Hi Harsha, > > On Thu, 28 Jun 2018 at 1

RE: [PATCH v3 weston 3/5] compositor-drm: add support for CTM property

2018-07-24 Thread Harsha Manjula Mallikarjun (RBEI/ECF3)
> -Original Message- > From: Daniel Stone [mailto:dan...@fooishbar.org] > Sent: Saturday, July 21, 2018 5:48 PM > To: Harsha Manjula Mallikarjun (RBEI/ECF3) > > Cc: wayland > Subject: Re: [PATCH v3 weston 3/5] compositor-drm: add support for CTM > property > > Hi Harsha, > > On Thu, 28

Re: [RFC libinput] dox: switch to sphinx for the user-visible documentation

2018-07-24 Thread Daniel Stone
Hey, On Tue, 24 Jul 2018 at 06:43, Peter Hutterer wrote: > Sending this out as patch even though what really matters is the > output. Which is... here, tadaaa! > > https://people.freedesktop.org/~whot/libinput-rtd/ > > Basically the motivation here is to make the user-visible documentation less >

Re: Implementing right click and middle click drag

2018-07-24 Thread Peter Hutterer
On Fri, Jul 20, 2018 at 11:10:32AM +0530, Sagar Tewari wrote: > On Wed, Jul 18, 2018 at 1:52 PM Peter Hutterer > wrote: > > > > > I'm not sure about the WITH_LOCK and POTENTIAL_UNLOCK parts, they should be > > (in theory) the same as the existing ones where DRAGGING_WAIT goes back to > > DRAGGING