- Leap 42.3 merge
  * boo#1039812

• Files Changed
• Browse Source

- Update to version 0.25.1
  * Just one patch that's been sitting on master for a while now - 
    after a proximity event we immediately post a motion event. 
    This avoids the lines between the last known point before
    proximity out and the new point.

• Files Changed
• Browse Source

- Update to version 0.25.0 
  * fixing two bugs with tablet pad modes on kernel 4.9 and later. 
    First, we never successfully opened the sysfs files representing
    the LEDs, so they didn't update as the kernel would change them.
    Second, had we opened them correctly we would've likely crashed
    as the property update would have been sent from within the
    input thread.  Both issues are fixed now, together with a fix
    for a test case failure for ppc64/aarch64.

• Files Changed
• Browse Source

1

• Files Changed
• Browse Source

1

• Files Changed
• Browse Source

1

• Files Changed
• Browse Source

1

• Files Changed
• Browse Source

1

• Files Changed
• Browse Source

- install the driver by default; added "Supplements: xorg-x11-server"
  for this (bnc#999098)

- Update to version 0.19.1:
  + One of the property names had a clear typo in it, "Horizonal"
    instead of "Horizontal". This update corrects this property
    name.
  + A second patch was snuck in to avoid bug messages when
    submitting button numbers beyond what we can handle in the
    protocol.

• Files Changed
• Browse Source

- Update to version 0.19.0
  One significant change that affects packagers: the config snippet has been
  renamed from 90-libinput.conf to 60-libinput.conf.
  This should not show any immediate effects on most user's machines but there
  is a slight potential of user configurations to change if their custom
  snippets now sort after libinput instead of before.
  This change is part of the two-step solution to fix the handling of wacom
  tablets when the libinput driver is present. Previously, the libinput driver
  would overwrite any driver assigned to any supported devices. While it does
  not yet bind to tablet devices by default, some tablets also look like
  a keyboard, causing those devices to stop working. For those devices, the
  wacom driver is the better option.
  Since the X server is lacking an option to conditionally bind InputClass
  snippets based on current values (git master has a NoMatch* option), the
  safe alternative is to bump the libinput priority down and, at the same
  time, bump the wacom driver's priority up.
  For the cases where the wacom driver should not handle any device, simply
  uninstalling it is sufficient.
- refreshed n_enable-tapping.patch

• Files Changed
• Browse Source

- Update to version 0.18.0:
This release adds support for tablet tool devices. Now, this support should
be taken with a grain of salt, it works differently to the xf86-input-wacom
driver and thus some capability differences can be observed:
First, pad support is still missing, i.e. you cannot use the buttons on the
tablet bit itself.
There are no specific configuration options just yet, and the way we are
aiming for libinput support, many of the options you are used to may not
exist ever.
The most important part: tool support is handled dynamically. As a tool is
first brought into proximity, a new X device is created for that tool only
(no multiplexing of tools through the same X device). Clients may expect a
static list of tools, so for those you will need to bring the tool into
proximity before starting the client.
In short, do not use this driver for tablets on production workstations yet.

• Files Changed
• Browse Source

1

• Files Changed
• Browse Source

1

• Files Changed
• Browse Source

1

• Files Changed
• Browse Source

1

• Files Changed
• Browse Source

1

• Files Changed
• Browse Source

1

• Files Changed
• Browse Source

1

• Files Changed
• Browse Source

1

• Files Changed
• Browse Source

1

• Files Changed
• Browse Source