2017-06-29 08:40:28 +10:00
|
|
|
.TH libinput-debug-events "1" "" "libinput @LIBINPUT_VERSION@" "libinput Manual"
|
2015-04-30 12:41:50 +10:00
|
|
|
.SH NAME
|
2017-06-02 12:15:50 +10:00
|
|
|
libinput\-debug\-events \- debug helper for libinput
|
2015-04-30 12:41:50 +10:00
|
|
|
.SH SYNOPSIS
|
2018-10-31 15:52:25 +10:00
|
|
|
.B libinput debug\-events \fI[options]\fB
|
|
|
|
|
.PP
|
|
|
|
|
.B libinput debug\-events \fI[options]\fB \-\-udev \fI<seat>\fB
|
|
|
|
|
.PP
|
2019-11-25 12:22:19 +10:00
|
|
|
.B libinput debug\-events \fI[options]\fB [\-\-device] \fI/dev/input/event0\fB [\fI/dev/input/event1\fB...]
|
2015-04-30 12:41:50 +10:00
|
|
|
.SH DESCRIPTION
|
|
|
|
|
.PP
|
|
|
|
|
The
|
2017-06-02 12:15:50 +10:00
|
|
|
.B "libinput debug\-events"
|
2015-04-30 12:41:50 +10:00
|
|
|
tool creates a libinput context and prints all events from these devices.
|
|
|
|
|
.PP
|
|
|
|
|
This is a debugging tool only, its output may change at any time. Do not
|
|
|
|
|
rely on the output.
|
|
|
|
|
.PP
|
|
|
|
|
This tool usually needs to be run as root to have access to the
|
|
|
|
|
/dev/input/eventX nodes.
|
|
|
|
|
.SH OPTIONS
|
|
|
|
|
.TP 8
|
2017-07-03 13:33:20 +10:00
|
|
|
.B \-\-device \fI/dev/input/event0\fR
|
2019-11-25 12:22:19 +10:00
|
|
|
Use the given device(s) with the path backend. The \fB\-\-device\fR argument may be
|
2018-10-31 15:52:25 +10:00
|
|
|
omitted.
|
2017-06-19 17:13:38 +10:00
|
|
|
.TP 8
|
|
|
|
|
.B \-\-grab
|
|
|
|
|
Exclusively grab all opened devices. This will prevent events from being
|
|
|
|
|
delivered to the host system.
|
|
|
|
|
.TP 8
|
2017-06-02 12:15:50 +10:00
|
|
|
.B \-\-help
|
2015-04-30 12:41:50 +10:00
|
|
|
Print help
|
2017-04-20 11:04:44 +10:00
|
|
|
.TP 8
|
2017-06-19 17:13:38 +10:00
|
|
|
.B \-\-quiet
|
|
|
|
|
Only print libinput messages, don't print anything from this tool. This is
|
|
|
|
|
useful in combination with --verbose for internal state debugging.
|
|
|
|
|
.TP 8
|
2017-06-02 12:15:50 +10:00
|
|
|
.B \-\-show\-keycodes
|
2017-04-20 11:04:44 +10:00
|
|
|
Key events shown by this tool are partially obfuscated to avoid passwords
|
|
|
|
|
and other sensitive information showing up in the output. Use the
|
2017-06-02 12:15:50 +10:00
|
|
|
.B \-\-show\-keycodes
|
2017-04-20 11:04:44 +10:00
|
|
|
argument to make all keycodes visible.
|
2017-06-19 17:13:38 +10:00
|
|
|
.TP 8
|
2017-07-03 13:33:20 +10:00
|
|
|
.B \-\-udev \fI<seat>\fR
|
2017-06-19 18:38:33 +10:00
|
|
|
Use the udev backend to listen for device notifications on the given seat.
|
|
|
|
|
The default behavior is equivalent to \-\-udev "seat0".
|
2017-06-19 17:13:38 +10:00
|
|
|
.TP 8
|
|
|
|
|
.B \-\-verbose
|
|
|
|
|
Use verbose output
|
|
|
|
|
.SS libinput configuration options
|
|
|
|
|
.TP 8
|
2019-05-08 11:24:28 +10:00
|
|
|
.B \-\-apply-to="pattern"
|
|
|
|
|
Configuration options are only applied where the device name matches the
|
|
|
|
|
pattern. This pattern has no effect on the \fB\-\-disable-sendevents\fR
|
|
|
|
|
option.
|
|
|
|
|
.TP 8
|
2017-09-05 14:12:09 +10:00
|
|
|
.B \-\-disable-sendevents="pattern"
|
|
|
|
|
Set the send-events option to disabled for the devices matching patterns.
|
2019-05-08 11:24:28 +10:00
|
|
|
This option is not affected by the \fB\-\-apply-to="pattern"\fR option.
|
2017-09-05 14:12:09 +10:00
|
|
|
.TP 8
|
2017-06-19 17:13:38 +10:00
|
|
|
.B \-\-enable\-tap|\-\-disable\-tap
|
2017-07-03 13:33:20 +10:00
|
|
|
Enable or disable tap-to-click
|
2017-06-19 17:13:38 +10:00
|
|
|
.TP 8
|
|
|
|
|
.B \-\-enable-drag|\-\-disable\-drag
|
|
|
|
|
Enable or disable tap-and-drag
|
|
|
|
|
.TP 8
|
|
|
|
|
.B \-\-enable\-drag-lock|\-\-disable\-drag\-lock
|
2019-08-13 14:47:53 -07:00
|
|
|
Enable or disable drag-lock
|
2017-06-19 17:13:38 +10:00
|
|
|
.TP 8
|
|
|
|
|
.B \-\-enable\-natural\-scrolling|\-\-disable\-natural\-scrolling
|
2017-07-03 13:33:20 +10:00
|
|
|
Enable or disable natural scrolling
|
2017-06-19 17:13:38 +10:00
|
|
|
.TP 8
|
|
|
|
|
.B \-\-enable\-left\-handed|\-\-disable\-left\-handed
|
2017-07-03 13:33:20 +10:00
|
|
|
Enable or disable left handed button configuration
|
2017-06-19 17:13:38 +10:00
|
|
|
.TP 8
|
2017-11-15 13:32:30 +10:00
|
|
|
.B \-\-enable\-middlebutton|\-\-disable\-middlebutton
|
|
|
|
|
Enable or disable middle button emulation
|
|
|
|
|
.TP 8
|
2017-06-19 17:13:38 +10:00
|
|
|
.B \-\-enable\-dwt|\-\-disable\-dwt
|
2017-07-03 13:33:20 +10:00
|
|
|
Enable or disable disable-while-typing
|
2017-06-19 17:13:38 +10:00
|
|
|
.TP 8
|
2022-03-08 01:33:40 +00:00
|
|
|
.B \-\-enable\-dwtp|\-\-disable\-dwtp
|
|
|
|
|
Enable or disable disable-while-trackpointing
|
|
|
|
|
.TP 8
|
2019-12-05 15:11:03 +10:00
|
|
|
.B \-\-enable\-scroll-button-lock|\-\-disable\-scroll-button-lock
|
2019-03-20 10:56:51 +10:00
|
|
|
Enable or disable the scroll button lock
|
|
|
|
|
.TP 8
|
2018-04-06 08:18:06 +10:00
|
|
|
.B \-\-set\-click\-method=[none|clickfinger|buttonareas]
|
2017-06-19 17:13:38 +10:00
|
|
|
Set the desired click method
|
|
|
|
|
.TP 8
|
|
|
|
|
.B \-\-set\-scroll\-method=[none|twofinger|edge|button]
|
2017-07-03 13:33:20 +10:00
|
|
|
Set the desired scroll method
|
2017-06-19 17:13:38 +10:00
|
|
|
.TP 8
|
|
|
|
|
.B \-\-set\-scroll\-button=BTN_MIDDLE
|
2017-07-03 13:33:20 +10:00
|
|
|
Set the button to the given button code
|
2017-06-19 17:13:38 +10:00
|
|
|
.TP 8
|
Introduce custom acceleration profile
The custom acceleration profile allow the user to define custom
acceleration functions for each movement type per device, giving
full control over accelerations behavior at different speeds.
This commit introduces 2 movement types which corresponds to the
2 profiles currently in use by libinput.
regular filter is Motion type.
constant filter is Fallback type.
This allows possible expansion of new movement types for the
different devices.
The custom pointer acceleration profile gives the user full control over the
acceleration behavior at different speeds.
The user needs to provide a custom acceleration function f(x) where
the x-axis is the device speed and the y-axis is the pointer speed.
The user should take into account the native device dpi and screen dpi in
order to achieve the desired behavior/feel of the acceleration.
The custom acceleration function is defined using n points which are spaced
uniformly along the x-axis, starting from 0 and continuing in constant steps.
There by the points defining the custom function are:
(0 * step, f[0]), (1 * step, f[1]), ..., ((n-1) * step, f[n-1])
where f is a list of n unitless values defining the acceleration
factor for each velocity.
When a velocity value does not lie exactly on those points, a linear
interpolation of the two closest points will be calculated.
When a velocity value is greater than the max point defined, a linear
extrapolation of the two biggest points will be calculated.
Signed-off-by: Yinon Burgansky <51504-Yinon@users.noreply.gitlab.freedesktop.org>
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2022-12-13 00:23:59 +02:00
|
|
|
.B \-\-set\-profile=[adaptive|flat|custom]
|
2018-05-21 12:09:42 +10:00
|
|
|
Set pointer acceleration profile
|
2017-06-19 17:13:38 +10:00
|
|
|
.TP 8
|
|
|
|
|
.B \-\-set\-speed=<value>
|
|
|
|
|
Set pointer acceleration speed. The allowed range is [-1, 1].
|
Introduce custom acceleration profile
The custom acceleration profile allow the user to define custom
acceleration functions for each movement type per device, giving
full control over accelerations behavior at different speeds.
This commit introduces 2 movement types which corresponds to the
2 profiles currently in use by libinput.
regular filter is Motion type.
constant filter is Fallback type.
This allows possible expansion of new movement types for the
different devices.
The custom pointer acceleration profile gives the user full control over the
acceleration behavior at different speeds.
The user needs to provide a custom acceleration function f(x) where
the x-axis is the device speed and the y-axis is the pointer speed.
The user should take into account the native device dpi and screen dpi in
order to achieve the desired behavior/feel of the acceleration.
The custom acceleration function is defined using n points which are spaced
uniformly along the x-axis, starting from 0 and continuing in constant steps.
There by the points defining the custom function are:
(0 * step, f[0]), (1 * step, f[1]), ..., ((n-1) * step, f[n-1])
where f is a list of n unitless values defining the acceleration
factor for each velocity.
When a velocity value does not lie exactly on those points, a linear
interpolation of the two closest points will be calculated.
When a velocity value is greater than the max point defined, a linear
extrapolation of the two biggest points will be calculated.
Signed-off-by: Yinon Burgansky <51504-Yinon@users.noreply.gitlab.freedesktop.org>
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2022-12-13 00:23:59 +02:00
|
|
|
This only applies to the flat or adaptive profile.
|
|
|
|
|
.TP 8
|
|
|
|
|
.B \-\-set\-custom\-points="<value>;...;<value>"
|
|
|
|
|
Sets the n points defining a custom acceleration function
|
|
|
|
|
The points are defined in a semicolon-separated list of floating point
|
|
|
|
|
non-negative numbers. Defaults to "0.0;1.0".
|
|
|
|
|
This only applies to the custom profile.
|
|
|
|
|
.TP 8
|
|
|
|
|
.B \-\-set\-custom\-step=<value>
|
|
|
|
|
Sets the distance along the x-axis between each point, starting from 0.
|
|
|
|
|
Defaults to 1.0.
|
|
|
|
|
This only applies to the custom profile.
|
|
|
|
|
.TP 8
|
2023-02-18 21:12:13 +02:00
|
|
|
.B \-\-set\-custom\-type=[fallback|motion|scroll]
|
Introduce custom acceleration profile
The custom acceleration profile allow the user to define custom
acceleration functions for each movement type per device, giving
full control over accelerations behavior at different speeds.
This commit introduces 2 movement types which corresponds to the
2 profiles currently in use by libinput.
regular filter is Motion type.
constant filter is Fallback type.
This allows possible expansion of new movement types for the
different devices.
The custom pointer acceleration profile gives the user full control over the
acceleration behavior at different speeds.
The user needs to provide a custom acceleration function f(x) where
the x-axis is the device speed and the y-axis is the pointer speed.
The user should take into account the native device dpi and screen dpi in
order to achieve the desired behavior/feel of the acceleration.
The custom acceleration function is defined using n points which are spaced
uniformly along the x-axis, starting from 0 and continuing in constant steps.
There by the points defining the custom function are:
(0 * step, f[0]), (1 * step, f[1]), ..., ((n-1) * step, f[n-1])
where f is a list of n unitless values defining the acceleration
factor for each velocity.
When a velocity value does not lie exactly on those points, a linear
interpolation of the two closest points will be calculated.
When a velocity value is greater than the max point defined, a linear
extrapolation of the two biggest points will be calculated.
Signed-off-by: Yinon Burgansky <51504-Yinon@users.noreply.gitlab.freedesktop.org>
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2022-12-13 00:23:59 +02:00
|
|
|
Sets the type of the custom acceleration function.
|
|
|
|
|
Defaults to fallback.
|
|
|
|
|
This only applies to the custom profile.
|
2017-06-19 17:13:38 +10:00
|
|
|
.TP 8
|
|
|
|
|
.B \-\-set\-tap\-map=[lrm|lmr]
|
2017-07-03 13:33:20 +10:00
|
|
|
Set button mapping for tapping
|
2015-04-30 12:41:50 +10:00
|
|
|
.SH NOTES
|
|
|
|
|
.PP
|
|
|
|
|
Events shown by this tool may not correspond to the events seen by a
|
|
|
|
|
different user of libinput. This tool initializes a separate context.
|
2017-05-25 10:12:26 +10:00
|
|
|
.SH LIBINPUT
|
|
|
|
|
Part of the
|
|
|
|
|
.B libinput(1)
|
|
|
|
|
suite
|
