On Wed, Nov 11, 2015 at 02:01:38PM +0200, Pekka Paalanen wrote:
> On Tue, 10 Nov 2015 11:35:35 +
> Damien Lespiau wrote:
>
> > Something else I noticed on this thead:
> >
> > In the reply 20151019013047.GA8175@jelly.local from Peter, there's a
> > diff put there for reference, picked up as a
The tablet tip works like a button in the kernel but is otherwise not really
a button. Split it into an explicit tip up/down event instead.
Signed-off-by: Peter Hutterer
---
src/libinput-private.h | 7 +++
src/libinput.c | 42 ++
src/libinput.
Signed-off-by: Peter Hutterer
---
tools/event-debug.c | 7 +--
1 file changed, 5 insertions(+), 2 deletions(-)
diff --git a/tools/event-debug.c b/tools/event-debug.c
index 6e5f8a8..05fb1a7 100644
--- a/tools/event-debug.c
+++ b/tools/event-debug.c
@@ -490,8 +490,11 @@ print_proximity_event(s
Signed-off-by: Peter Hutterer
---
src/libinput.c | 2 +-
src/libinput.h | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/src/libinput.c b/src/libinput.c
index a05148f..79e4863 100644
--- a/src/libinput.c
+++ b/src/libinput.c
@@ -1101,7 +1101,7 @@ libinput_tool_get_type(struc
Signed-off-by: Peter Hutterer
---
test/tablet.c | 42 --
1 file changed, 36 insertions(+), 6 deletions(-)
diff --git a/test/tablet.c b/test/tablet.c
index 8048c70..5dcb9d3 100644
--- a/test/tablet.c
+++ b/test/tablet.c
@@ -167,6 +167,8 @@ START_TEST(proxim
We send the axis state in the proximity event so we don't send another axis
event for the same state. The first axis event is sent whenever the tool
moves. This is largely of note for test cases, in real-world usage a tool
cannot be held still enough to never send axis updates.
Signed-off-by: Pete
Signed-off-by: Peter Hutterer
---
test/litest.c | 12
1 file changed, 12 insertions(+)
diff --git a/test/litest.c b/test/litest.c
index d10175f..ce2a6a7 100644
--- a/test/litest.c
+++ b/test/litest.c
@@ -1898,6 +1898,7 @@ static void
litest_print_event(struct libinput_event *event)
Behavior for axis events in the same event frame as the BTN_TOUCH is to
always send axis events before any tip state.
Behavior for button events in the same event frame as the BTN_TOUCH is to
order button events to happen when the tip is in proximity, i.e. after the tip
event on tip down and before
Signed-off-by: Peter Hutterer
---
src/evdev-tablet.c | 6 +++---
src/evdev-tablet.h | 2 +-
2 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/src/evdev-tablet.c b/src/evdev-tablet.c
index 04cd082..72ec31d 100644
--- a/src/evdev-tablet.c
+++ b/src/evdev-tablet.c
@@ -496,9 +496,9 @@ ta
On Tue, 10 Nov 2015 11:35:35 +
Damien Lespiau wrote:
> Something else I noticed on this thead:
>
> In the reply 20151019013047.GA8175@jelly.local from Peter, there's a
> diff put there for reference, picked up as a patch by patchwork:
>
>
> http://patchwork.freedesktop.org/patch/msgid/20
On Tue, 10 Nov 2015 11:35:35 +
Damien Lespiau wrote:
> On Mon, Nov 09, 2015 at 11:25:17AM +0200, Pekka Paalanen wrote:
> > Hi Damien,
>
> Hi Pekka,
>
> > I just noticed that from this patch series of three, only 1/3 shows up
> > in Patchwork as http://patchwork.freedesktop.org/patch/64191/
11 matches
Mail list logo