A new release of libinput, 0.13.0, is now available. No API changes were
merged in this release, the ABI is compatible with 0.12.0.
The tap motion threshold is now a fixed distance on all touchpads (with
physical resolution). This stops the delay in pointer motion seen on some
devices.
The edge s
On 22/03/15 09:32 PM, Jonas Ådahl wrote:
> On Fri, Mar 20, 2015 at 04:44:41PM -0500, Derek Foreman wrote:
>> Currently we unmap and re-map the cursor when the hotspot changes which
>> causes spurious enter/leave events.
>>
>> This changes the pointer_set_cursor() logic to avoid this.
>>
>> Signed-o
Currently we unmap and re-map the cursor when the hotspot changes which
causes spurious enter/leave events.
This changes the pointer_set_cursor() logic to avoid this.
Signed-off-by: Derek Foreman
---
Remove comments and unnecessary variable.
src/input.c | 36 --
On 03/23/2015 04:22 AM, Giulio Camuffo wrote:
2015-03-23 12:00 GMT+02:00 Marek Chalupa :
Destroyed seems confusing to me too, since the resource is not really
destroyed. What about inert or unalive ?
Inert is ok, imho. On the client side they are called zombie
objects... maybe for consistency
On Mon, 23 Mar 2015 07:21:24 -0400
Marek Chalupa wrote:
> Hi,
>
> On Thu, Mar 19, 2015 at 10:51 AM, Pekka Paalanen
> wrote:
>
> > On Thu, 19 Mar 2015 03:38:52 -0400
> > Marek Chalupa wrote:
> >
> > > Test misc races when adding/releasing devices. One of the
> > > tests reveals a race that is
2015-03-23 12:00 GMT+02:00 Marek Chalupa :
> Destroyed seems confusing to me too, since the resource is not really
> destroyed. What about inert or unalive ?
Inert is ok, imho. On the client side they are called zombie
objects... maybe for consistency it'd be better to keep that here too.
>
> On
Hi,
On Thu, Mar 19, 2015 at 10:51 AM, Pekka Paalanen
wrote:
> On Thu, 19 Mar 2015 03:38:52 -0400
> Marek Chalupa wrote:
>
> > Test misc races when adding/releasing devices. One of the
> > tests reveals a race that is not currently handled by Weston.
> >
> > Signed-off-by: Marek Chalupa
> > ---
Hi,
On 23-03-15 05:29, Peter Hutterer wrote:
Except for a few axes where this may be correct, a min == max axis range
indicates a broken kernel driver. To avoid potential divisions by zero when
scaling this axis later, reject such a device outright.
Signed-off-by: Peter Hutterer
Looks good:
Hi,
On 23-03-15 02:50, Peter Hutterer wrote:
This reverts commit 0e64837f30c310da878f28961a6db7c4bcd4f282.
Rather than a customized touchpad property, let udev handle this and set the
absinfo struct during the normal setup procedures. No need for libinput to
have a custom workaround here.
Sign
On Fri, 20 Mar 2015 15:26:53 +0100
Jonny Lamb wrote:
> Reviewed-by: Derek Foreman
> Reviewed-by: Bryce Harrington
> ---
> clients/nested-client.c | 7 +++
> clients/simple-egl.c | 7 ---
> clients/subsurfaces.c | 6 +++---
> clients/window.c | 8
> shar
On Fri, 20 Mar 2015 15:26:52 +0100
Jonny Lamb wrote:
> Reviewed-by: Derek Foreman
> Reviewed-by: Bryce Harrington
> ---
> src/compositor-drm.c | 3 ++-
> src/compositor-fbdev.c | 2 +-
> src/compositor-wayland.c | 1 +
> src/compositor-x11.c | 5 +
> src/gl-renderer.c
On Fri, 20 Mar 2015 15:26:51 +0100
Jonny Lamb wrote:
> Reviewed-by: Derek Foreman
> Reviewed-by: Bryce Harrington
> ---
> Makefile.am | 4 ++-
> clients/nested-client.c | 4 ++-
> clients/simple-egl.c | 6 +++-
> clients/subsurfaces.c | 5 ++-
> clients/window.c
Hi,
sorry to come to this after it has already landed. I have some comments
here. It's mostly just clean-ups and simplifications, though.
On Fri, 20 Mar 2015 15:26:50 +0100
Jonny Lamb wrote:
> Reviewed-by: Derek Foreman
> Reviewed-by: Bryce Harrington
> ---
> src/compositor-drm.c | 13 +
Destroyed seems confusing to me too, since the resource is not really
destroyed. What about inert or unalive ?
On Thu, Mar 19, 2015 at 2:34 PM, Bill Spitzak wrote:
> I think the name "intact" is really confusing. Can it be instead called
> "destroyed"?
>
>
> On 03/19/2015 01:11 AM, Marek Chalupa
Il 23/03/2015 09:12, Pekka Paalanen ha scritto:
IMO no space, please. Without a space it looks more like the actual
operator precedence in C... doesn't it? I hope I remember the
precedence rules right here.
fwiw with a space is currently much more widely used in Weston. Not a
great test but no
Am 20.03.2015 15:24, schrieb Pekka Paalanen:
On Fri, 20 Mar 2015 15:13:43 +0100
Thilo Cestonaro wrote:
Am 20.03.2015 12:54, schrieb Thilo Cestonaro:
> Am 20.03.2015 11:32, schrieb Thilo Cestonaro:
>> Further debuggin.
>>
>> I added some debug output to weston-launch.
>> When the parent part (o
On Mon, 23 Feb 2015 12:14:51 -0600
Derek Foreman wrote:
>
> I'm suddenly unsure what our coding style is regarding typecasts, I'd
> thought we didn't put a space between cast and value, but there are
> places where we do in the existing code - as well of plenty of examples
> with no space.
>
>
On Sun, Mar 22, 2015 at 8:57 PM, Jonas Ådahl wrote:
> On Mon, Mar 23, 2015 at 01:21:38PM +1000, Peter Hutterer wrote:
>> On Mon, Mar 23, 2015 at 10:23:18AM +0800, Jonas Ådahl wrote:
>> > On Mon, Mar 09, 2015 at 01:28:04PM +1000, Peter Hutterer wrote:
>> > > The axis source determines how an event
18 matches
Mail list logo
