On 9 November 2015 at 18:17, Bill Spitzak wrote:
> Making the transform into a bitfield allows bitfield tests for useful facts:
> it can see if it is a mirror image by testing the flip bit, and check for
> transposition of the axes by checking the 90 degree bit. I believe this is
> the reason behi
On Fri, Nov 13, 2015 at 10:17:15PM +0100, Carlos Garnacho wrote:
> Hey,
>
> On Fri, Nov 6, 2015 at 5:24 AM, Peter Hutterer
> wrote:
> > Signed-off-by: Peter Hutterer
> > ---
> > This is the revamped version of the tablet protocol for graphics tablets
> > (e.g. Wacom tablets). Too many changes f
On Sun, Nov 15, 2015 at 9:48 PM, Auke Booij wrote:
> On 9 November 2015 at 18:17, Bill Spitzak wrote:
>> Making the transform into a bitfield allows bitfield tests for useful facts:
>> it can see if it is a mirror image by testing the flip bit, and check for
>> transposition of the axes by checki
libinput 1.1.1 is now available.
Two significant fixes and a couple of other cleanups.
* pointer acceleration is now initialized for pointer-like device without
buttons. Some devices have rel x/y axes but no buttons and aren't tagged
as pointers by udev. If such a device sent an event it could
Signed-off-by: Peter Hutterer
---
src/libinput.c | 49 +
1 file changed, 49 insertions(+)
diff --git a/src/libinput.c b/src/libinput.c
index c47f9fc..ed9490f 100644
--- a/src/libinput.c
+++ b/src/libinput.c
@@ -1064,48 +1064,97 @@ libinput_event_ta
Signed-off-by: Peter Hutterer
---
src/evdev-tablet.c | 13 +++-
src/libinput-private.h | 2 +
src/libinput.c | 9 ++-
test/tablet.c | 170 +
4 files changed, 192 insertions(+), 2 deletions(-)
diff --git a/src/evdev-tablet.
By definition, the state is always proximity in on other events but let's
allow the call to be made anyway.
Signed-off-by: Peter Hutterer
---
src/libinput.c | 6 ++
1 file changed, 6 insertions(+)
diff --git a/src/libinput.c b/src/libinput.c
index ed9490f..a2a98cc 100644
--- a/src/libinput.
On 6 November 2015 at 04:24, Peter Hutterer wrote:
> Signed-off-by: Peter Hutterer
> ---
> This is the revamped version of the tablet protocol for graphics tablets
> (e.g. Wacom tablets). Too many changes from the last version (a year ago or
> so), so I won't detail them, best to look at it with
The frame event groups separate pointer events together. The primary use-case
for this at the moment is diagonal scrolling - a vertical/horizontal scroll
event can be grouped together to calculate the correct motion vector.
Frame events group all wl_pointer events. An example sequence of motion eve
Signed-off-by: Peter Hutterer
---
desktop-shell/shell.c | 8 +---
1 file changed, 1 insertion(+), 7 deletions(-)
diff --git a/desktop-shell/shell.c b/desktop-shell/shell.c
index 52d1195..9968307 100644
--- a/desktop-shell/shell.c
+++ b/desktop-shell/shell.c
@@ -3303,13 +3303,7 @@ static void
On Sun, Nov 15, 2015 at 11:50:26PM +, Auke Booij wrote:
> On 6 November 2015 at 04:24, Peter Hutterer wrote:
> > Signed-off-by: Peter Hutterer
> > ---
> > This is the revamped version of the tablet protocol for graphics tablets
> > (e.g. Wacom tablets). Too many changes from the last version
On Mon, Nov 16, 2015 at 12:35:57PM +1000, Peter Hutterer wrote:
> Signed-off-by: Peter Hutterer
Reviewed-by and pushed, thanks:
To ssh://jad...@git.freedesktop.org/git/wayland/weston
64d78bb..1118952 master -> master
Jonas
> ---
> desktop-shell/shell.c | 8 +---
> 1 file changed, 1 i
Signed-off-by: Peter Hutterer
---
This one goes with v6 of the protocol, see
http://patchwork.freedesktop.org/patch/64871/
Changes to v1:
- revamped for wl_pointer.frame (instead of axis frame)
- added the hooks for the tests
- rebased on master, added the new pointer axis grab handling bits
- re
On Mon, Nov 16, 2015 at 10:57:24AM +1000, Peter Hutterer wrote:
> The frame event groups separate pointer events together. The primary use-case
> for this at the moment is diagonal scrolling - a vertical/horizontal scroll
> event can be grouped together to calculate the correct motion vector.
> Fra
Hey,
I took a look at how the currently internal, but to be made external,
API looks like, and I wonder if it really should be this low level.
For the unaccelerated/accelerated/relative/absolute pointer events, I
made an event struct that is passed around and input.c takes that one
and emits the
On Mon, Nov 16, 2015 at 03:38:13PM +0800, Jonas Ådahl wrote:
> Hey,
>
> I took a look at how the currently internal, but to be made external,
> API looks like, and I wonder if it really should be this low level.
>
> For the unaccelerated/accelerated/relative/absolute pointer events, I
> made an e
16 matches
Mail list logo