libinput-a...-slot-delta(1)

πŸ“¦
version 1.32.0 Β· 2 versions
, in alpine 3.24, arch rolling, centos-stream 10, debian trixie, fedora 43, fedora 44, nixos 26.05, nixpkgs unstable, opensuse-leap 16.0, ubuntu questing, ubuntu resolute, ubuntu stonking

πŸ’– libinput-analyze-per-slot-delta πŸ’–

okay bestie, so this one is a page from the General Commands Manual β€” it's libinput-analyze-per-slot-delta, and yes that name is a whole mouthful, we're just gonna vibe with it. 🫢


✨ NAME ✨

libinput-analyze-per-slot-delta β€” analyze the per-event delta movement for touch slots


🌸 SYNOPSIS 🌸

libinput analyze per-slot-delta [--help] [options] recording.yml

πŸ¦‹ DESCRIPTION πŸ¦‹

The libinput analyze per-slot-delta tool looks at a recording you made with libinput record and prints out the delta movement per touch slot. that's it, that's the whole job. πŸ’…

⚠️ lowkey important: this is a debugging tool only. its output may change at any time. do not rely on the output. like, at all. no cap. 😭

πŸŽ€ OPTIONS πŸŽ€

  • --help β€” prints help, iconic, we love a supportive flag 🫢
  • --ignore-below=<units or mm> β€” ignore any movement that's below the threshold you give it. the threshold is in mm if --use-mm is selected, otherwise it's in device units. pick your fighter. ✨
  • --show-distance β€” also show the distance relative to the initial position of the current touch. that distance is in mm if --use-mm is selected, otherwise device units. ✨
  • --threshold=<units or mm> β€” colors any movement above this threshold in red. threshold is in mm if --use-mm is selected, otherwise device units. it's giving dramatic highlight. πŸ”₯
  • --use-mm β€” print data in mm instead of device units
  • --use-st β€” use the single-touch ABS_X/ABS_Y instead of the multitouch axes
  • --use-absolute β€” print absolute coordinates, not deltas

🌈 OUTPUT 🌈

here's an example output for a single finger touch on a touchpad that supports two slots. this one was made with the --use-mm flag. πŸ’–

 0.000000   +0ms TOU:     ++++++     |  ************* |
 0.021900  +21ms TOU: β†’β†˜ +1.10/+0.14 |  ************* |
 0.033468  +11ms TOU: β†’β†˜ +1.15/+0.19 |  ************* |
 0.043856  +10ms TOU: β†’β†˜ +1.76/+0.22 |  ************* |
 0.053237   +9ms TOU: β†’β†˜ +2.20/+0.19 |  ************* |

the ++++++ entry means a finger has been put down, and ------ means the finger has lifted. the left-most column is the absolute timestamp in seconds.microseconds, followed by the relative time of the event compared to the previous event. ⏱️

the word TOU in this example represents BTN_TOUCH β€” and similar abbreviations exist for BTN_TOOL_DOUBLETAP, BTN_TOOL_TRIPLETAP, BTN_TOOL_QUADTAP, and BTN_TOOL_QUINTTAP. so many tools, so little time. πŸ™ˆ

the arrows show the approximate direction on a 16-point compass β€” in this example, EastSouthEast. 🧭

each multitouch slot the hardware supports gets its own column, and that column shows asterisks ******** when no finger is down for that slot. where the column shows spaces only, a finger is down but no data is currently available. the way that's such a mood. πŸ’€

in the example above, the third event occurs ~33ms into the recording, is 11ms after the previous event, and has an east south-east direction. the movement for this event was x: 1.15 and y: 0.19 mm. a second finger is not currently down. ⭐


πŸ‘‘ LIBINPUT πŸ‘‘

part of the libinput(1) suite ✨


and that's the whole page bestie, you ate it up. this little slice of the General Commands Manual is signed off as libinput-a...-slot-delta(1) β€” go forth and analyze those slots, main character. πŸŽ€πŸ’œπŸ¦‹