[PATCH v2 libinput] Add an API to change pointer acceleration profiles

The quartett of new config functions is: libinput_device_config_accel_get_profiles libinput_device_config_accel_get_profile libinput_device_config_accel_set_profile libinput_device_config_accel_get_default_profile The profile defines how the pointer acceleration wo

Re: [PATCH libinput] Fix leaking device groups

On Mon, Sep 07, 2015 at 11:48:22AM +0800, Jonas Ådahl wrote: > On Mon, Sep 07, 2015 at 01:11:11PM +1000, Peter Hutterer wrote: > > If a caller has a reference to a device group when the context is destroyed, > > the memory for the group is never released. Calling > > libinput_device_group_unref() w

[PATCH libinput] Add an API to change pointer acceleration profiles

The quartett of new config functions is: libinput_device_config_accel_get_profiles libinput_device_config_accel_get_profile libinput_device_config_accel_set_profile libinput_device_config_accel_get_default_profile The profile defines how the pointer acceleration wor

Re: [PATCH libinput] Fix leaking device groups

On Mon, Sep 07, 2015 at 01:11:11PM +1000, Peter Hutterer wrote: > If a caller has a reference to a device group when the context is destroyed, > the memory for the group is never released. Calling > libinput_device_group_unref() will release it and there are no side-effects > since the group has no

[PATCH libinput] Fix leaking device groups

If a caller has a reference to a device group when the context is destroyed, the memory for the group is never released. Calling libinput_device_group_unref() will release it and there are no side-effects since the group has no back-references. It's inconsistent with the rest of libinput though - a

Re: [PATCH libinput] libinput: add orientation and size of touch point and pressure to the API

On Wed, Sep 02, 2015 at 12:50:47PM +0200, Andreas Pokorny wrote: > Hi, > > On Tue, Sep 1, 2015 at 8:30 AM, Peter Hutterer > wrote: > > > [...] > > but first up, I have to ask: how did you test this, do you have an > > implementation higher up in the stack that makes use of this? The API looks >

Re: [PATCH libinput] Fix premature flushing of evdev event on mx4 touchscreen

On Sun, Sep 06, 2015 at 02:59:07PM +0200, Andreas Pokorny wrote: > The mx4 touchscreen driver emits BTN_TOUCH and BTN_TOOL_FINGER key events > on a new contact. Prior to this patch only the BTN_TOUCH event was filtered > out. Now the whole range of BTN_ events for tool types and certain builtin > m

Re: [PATCH libinput] fix gcc warning on unused return value

On Fri, Sep 04, 2015 at 01:35:01PM +0200, Andreas Pokorny wrote: > > Signed-off-by: Andreas Pokorny merged, thanks Cheers, Peter > --- > test/litest.c | 8 +--- > 1 file changed, 5 insertions(+), 3 deletions(-) > > diff --git a/test/litest.c b/test/litest.c > index 29e764b..38e313e 10

[PATCH libinput] Fix premature flushing of evdev event on mx4 touchscreen

The mx4 touchscreen driver emits BTN_TOUCH and BTN_TOOL_FINGER key events on a new contact. Prior to this patch only the BTN_TOUCH event was filtered out. Now the whole range of BTN_ events for tool types and certain builtin multi finger gestures are marked as non-key type. This patch is based on

[PATCH libinput 2/2] extend tools to print and display touch event properties

event-gui draws the touch contact as two concentric ellipses that indicate contact pressure through oppacity. Signed-off-by: Andreas Pokorny --- tools/event-debug.c | 30 -- tools/event-gui.c | 30 -- 2 files changed, 56 insertions(+), 4

[PATCH libinput 1/2] libinput: add orientation and size of touch point and pressure to the API

This change adds four new properties to touch events: * major: diameter of the touch ellipse along the major axis * minor: diameter perpendicular to major axis * pressure: a pressure value mapped into the range [0, 1] * orientation: the angle between major and the x axis [0, 360] Those values are

[PATCH libinput v7 0/2] add orientation, size and pressure of touch

Hi, I cannot believe this is v7, but here it goes. This version solves the problem with the missing initial values for the added slot data. I dumped the 'available data' flag set. Doxygen wording should be consistent now. Since you indicated that you would redo some of the texts anyhow I left the a