On Fri, Mar 20, 2015 at 09:54:30AM +0100, Hans de Goede wrote:
Hi,
On 20-03-15 01:38, Peter Hutterer wrote:
On Fri, Mar 20, 2015 at 10:19:06AM +1000, Peter Hutterer wrote:
[...]
5) If a device has multiple axes of the same type, is the order
supposed to be ABI? Example: gamepads tend to
Now that we've removed the XYToWindow handler in Xwayland, we actually
have to stack windows properly. This stacks windows on top when
activating them.
Note that for a fully robust Xwayland implementation, we'll need a
complete stack tracker implementation, unfortunately.
---
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.
Signed-off-by: Peter Hutterer
On Mon, Mar 09, 2015 at 01:28:04PM +1000, Peter Hutterer wrote:
The axis source determines how an event was generated. That enables clients to
judge when to use kinetic scrolling.
Nice to see this happening!
I have not looked at the implementation so far, only the protocol. I have
some
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-off-by: Derek Foreman der...@osg.samsung.com
---
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 was generated. That enables clients
to
judge when to use kinetic scrolling.
Nice to see this happening!
I have not
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 was generated. That enables
clients to
judge when to use
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 peter.hutte...@who-t.net
---
src/evdev.c | 34
