04209b9c35
- Update to version 1.5.0: * the compose and kana LEDs are now supported * tablet tools now have a property to indicate the tool serial and hw id (if any) * libinput's tablet tool pressure range config is now supported * libinput's clickfinger button map config is now supported * we remap some higher keycodes to FK20 and friends, paving the way for systemd/udev to map those properly in their hwdb files
Stefan Dirsch2024-10-17 23:33:12 +00:00
4b2b9be3e3
Accepting request 1105974 from X11:XOrg
Ana Guerrero2023-08-30 08:19:04 +00:00
3983aa7009
Accepting request 1105937 from home:iznogood:branches:X11:XOrg
Stefan Dirsch2023-08-26 03:58:04 +00:00
ce24cbfe3d
- Update to version 1.3.0 The main feature in this version is support for the new 'custom' pointer acceleration profile in libinput 1.23.0. This acceleration profile is quite flexible, so it is exposed via several properties: - "libinput Accel Custom Fallback Points" and "libinput Accel Custom Fallback Step" - "libinput Accel Custom Motion Points" and "libinput Accel Custom Motion Step" - "libinput Accel Custom Scroll Points" and "libinput Accel Custom Scroll Points" For details on what these mean, please see the man page and the libinput documentation: https://wayland.freedesktop.org/libinput/doc/latest/pointer-acceleration.html In addition, the "libinput Accel Profiles Available" and "libinput Accel Profile Enabled" properties have been expanded to 3 values. For backwards compatibility, the "libinput Accel Profile Enabled" continues to support setting 2 values only.
Stefan Dirsch2023-04-04 12:19:23 +00:00
562cacde21
Accepting request 949020 from home:iznogood:branches:X11:XOrg
Stefan Dirsch2022-01-25 13:36:22 +00:00
c79639ee43
- Update to version 1.2.1 * few typos and misc minor fixes * property added to turn off new high-resolution wheel scrolling API
Stefan Dirsch2022-01-24 10:32:01 +00:00
3bef6188cf
- reverted previous change; the issue was broken ckb-next, not the usage of libinput v120 API (boo#1190646)
Stefan Dirsch2021-10-08 12:02:16 +00:00
300420464a
- switch to libinput v120 API broke the driver, so disable it for now via patching config.h in specfile after running configure (boo#1190646)
Stefan Dirsch2021-10-05 11:44:07 +00:00
1e66316aac
- Update to version 1.2.0 * This release introduces support for touchpad gestures that will be available as part of X server 21.1. Additionally high-resolution scrolling data is now acquired from libinput if available and sent downstream to X server. The default scroll distance has been bumped to 120 in the process, but this should not affect correctly written clients.
Stefan Dirsch2021-09-20 09:33:05 +00:00
421fb363d7
- Update to version 1.1.0 * This release adds a new driver-specific option: ScrollPixelDistance. This option converts movement "pixels" from libinput into the server's "scroll unit" definition and can thus help speeding up or slowing down two-finger/edge scrolling.
Stefan Dirsch2021-06-23 23:18:10 +00:00
bbbebbc1a4
- Update to version 1.0.1 * Only one fix, the code to set the tap button mapping property didn't correctly check for a valid device, causing memory corruption and a crash if called after a device was disabled. Or, in more user-friendly terms: if your X session crashed after calling xinput disable $touchpad-device, this release has the fix for it.
Stefan Dirsch2021-04-16 13:28:09 +00:00
c45a03fb3d
Accepting request 883203 from X11:XOrg
Richard Brown
2021-04-08 19:03:08 +00:00
166423dd5f
- Update to version 1.0.0 * The biggest change here is the license change to MIT. Due to an unfortunate copy/paste error, the actual license text used was the Historical Permission Notice and Disclaimer license. With the ack of the various contributors, the driver is now using the MIT license text as intended. The actual impact is low, the HPND is virtually identical to the MIT license anyway (ianal, consult your legal dept if you have one). * The only other notable change: cancelled touch points are now lifted correctly. Where libinput cancels a touch, e.g. in response to a palm being detected, the touch point previously got stuck in the down state. This is fixed now.
Stefan Dirsch2021-04-06 08:35:17 +00:00
629b28867c
Accepting request 878736 from X11:XOrg
Richard Brown
2021-03-16 14:41:48 +00:00
52b8903dc7
Accepting request 878651 from home:dirkmueller:Factory
Stefan Dirsch2021-03-13 12:13:05 +00:00
da1c5f6d0c
- Update to version 0.30.0 * Only one noticeable change: the scroll button lock configuration option available in recent libinput versions is now exposed as the usual set of properties by this driver.
Stefan Dirsch2020-05-19 10:41:02 +00:00
67df01cd1d
- Update to version 0.29.0 * Only one real fix: we now check for the tool type as well as the serial when we create subdevices for tablet tools. Previously there were some cases where the eraser device wasn't created correctly.
Stefan Dirsch2019-08-20 13:05:51 +00:00
93f8206429
- Update to version 0.28.1 * This release contains a bugfix that will likely trigger in future releases of libinput. The driver assumed wrongly that any wheel event has a nonzero discrete event and used the discrete as a divisor. Which is obviously a bad idea, mathematically speaking, because you never know what the future will bring. Hint: it will bring wheel events with a discrete of zero.
Stefan Dirsch2019-02-04 17:45:42 +00:00
60a16a0f40
- Update to version 0.28.1 * Only two commits, only one that really matters: previously the driver used the per-device slot number to fetch the tracking IDs from a driver-internal array. Because devices re-use slots, this could cause a tracking ID mismatch when two touchscreens had the finger down at the same time. This is now fixed by switching to libinput's seat-wide slot number instead.
Stefan Dirsch2018-10-15 18:17:18 +00:00
4a560c7830
- Update to version 0.28.0 * This version adds a feature to expose the touch count for touch devices through the X device. It makes it possible for clients to adjust their UI based on the number of supported touches by this device. * Also, the draglock code had a bug and would call memset with an invalid size, causing memory corruption. You're advised to update, especially if you expect someone to use the draglock options.
Stefan Dirsch2018-07-11 10:50:34 +00:00
03076ec34f
- Update to version 0.27.1 * Just one bugfix, a regression introduced by the new property handling in 0.27.0 caused the property to toggle left-handed to not be initialized on all devices that required it. - supersedes U_Fix-left-handed-property.patch
Stefan Dirsch2018-04-12 09:50:33 +00:00
e1e68c4407
Accepting request 593847 from home:iznogood:branches:X11:XOrg
Stefan Dirsch2018-04-05 18:46:37 +00:00
6ef75211ed
- Update to version 0.27 * The libinput driver splits libinput devices into multiple X devices (e.g. a mouse and a keyboard device) and then routes the events accordingly. In the case where there is a user- specific on one device, a VT switch or suspend/resume cycle sometimes overwrote the configuration with the devices in-order, resulting in the loss of that configuration. e.g. if the keyboard device resumes after the mouse device, the natural scroll setting may get overwritten with the default. This is fixed now. And a note to the man page, we don't support specifying devices as /dev/input/by-id or /dev/input/by-path. It's not worth the effort, so at least point this out in the man page.
Stefan Dirsch2018-04-04 12:38:20 +00:00
faba0c49a5
- Update to version 0.26 * A few patches that have been sitting on master for a while, of which two are documentation patches. The most interesting patch is for tablets: previously we didn't send a separate motion event before the button event which caused some clients to trigger the button event on the previous stylus position. - obsoletes U_Only-initialize-properties.patch
Stefan Dirsch2017-09-19 08:39:52 +00:00
6479346c55
- 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.
Stefan Dirsch2017-05-05 10:04:49 +00:00
b248940bad
- 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.
Stefan Dirsch2017-03-09 10:41:17 +00:00
593e080cc8
- 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
Stefan Dirsch2016-04-28 14:00:14 +00:00
c03df4632c
- 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.
Stefan Dirsch2016-04-07 15:37:20 +00:00
8a383b7306
Accepting request 349138 from home:Zaitor
Stefan Dirsch2015-12-16 13:27:07 +00:00
069732d7b5
- Update to version 0.15.0: This release adds new properties to select the pointer acceleration profile. See the libinput documentation for more details http://wayland.freedesktop.org/libinput/doc/latest/pointer-acceleration.html Note that this driver now installs a xorg.conf.d snippet in the usual locations. This snippet will assign libinput to mouse, touchpad, keyboard and touch devices but will skip tablets and joysticks (we don't support thoss in libinput yet). The filename of the snippet means it will sort after evdev and synaptics and thus override either driver. - n_enable-tapping.patch * enables tapping for touchpads in upstream xorg.conf.d snippet - removed superseded xorg.conf.d snippet
Stefan Dirsch2015-12-15 13:50:20 +00:00
9af34db495
Accepting request 334128 from X11:XOrg
Stephan Kulow
2015-09-30 03:52:36 +00:00
cef34a1bbc
Accepting request 334009 from home:pluskalm:branches:X11:XOrg
Stefan Dirsch2015-09-27 17:58:04 +00:00
1e62ed4c6e
Accepting request 308429 from home:Zaitor:branches:X11:XOrg
Stefan Dirsch2015-05-23 08:38:23 +00:00
4cd6a03e23
Accepting request 303797 from X11:XOrg
Stephan Kulow
2015-04-25 07:54:13 +00:00
96c74fc2fc
- xf86-input-libinput 0.9.0 * A couple of cosmetic changes but one addition of a new set of properties: properties named "libinput something Default" show the libinput default for a device. For example: libinput Click Methods Available (284): 1, 1 libinput Click Method Enabled (285): 0, 1 libinput Click Method Enabled Default (286): 1, 0 This device has software buttons and clickfingers available, clickfingers is currently enabled, software buttons is the default for this device.
Stefan Dirsch2015-04-24 15:22:48 +00:00
Ana Guerrero
Stefan Dirsch
Dominique Leuenberger
Richard Brown
Stephan Kulow