syngesture VS TPMouse

I've shared my opinion on why mouse/trackpad handling is terrible on most Linux distributions [0], thanks to an insane obsession w/ rewriting the entire stack and throwing away vendor-provided acceleration curves in order to provide gesture support, instead of just building it on top of the correct, working solution.

More importantly, there is a solution for fixing this and I've done my part by open sourcing a multi-touch gesture support that's driver-agnostic and runs on top of the vendor-provided drivers w/ their correct acceleration curves [1].

(But TBH I don't know if this applies to Apple's trackpad because I don't know if there are any first-party drivers w/ proper acceleration curves for Linux or if they've all been poorly reverse engineered.)

[0]: https://neosmart.net/blog/multi-touch-gestures-on-linux/

[1]: https://github.com/mqudsi/syngesture/

I wrote a general purpose multitouch daemon w/ gesture support for Linux that works with the existing input stack (i.e. doesn’t require switching to evinput), if anyone is interested:

https://neosmart.net/blog/2020/multi-touch-gestures-on-linux...

https://github.com/mqudsi/syngesture

Regardless of software (touchegg + touché, fusuma, libinput-gestures + libinput-gestures-qt OR gestures, gebaar-libinput, gebaar-libinput-fork, syngesture, gestures), which gestures do you actively use on your Plasma desktop?

And for Windows, my https://github.com/esporttoys/TPMouse was inspired by warpd itself but focuses more on the intuitive usability of direct cursor control via inertia/momentum.

You may be interested in how I did my Windows script for adding three-finger drag[0].

Basically, it is an independent subscriber to RawInput messages that only keeps track of whether or not to send three-finger drag, and posts emulated mouse messages using SendInput. I have a few other scripts that each run as independent userland processes that only monitors their own trigger and nothing else.

Tangentially, not sure if this might serve for some inspiration, but my TPMouse[1] script implemented inertia in a framerate-independent way so that it uses very little resource while having perfect simulation stability.

A previous discussion where I explained the analytic derivation for this low-resource exact-solution damped inertia can be seen in [10]

[0] https://github.com/EsportToys/PrecisionThreeFingerDrag/blob/...

[1] https://github.com/EsportToys/TPMouse

[10] https://old.reddit.com/r/Trackballs/comments/ym9q2t/tpmouse_...

With the TPMouse script I implemented the activation shortcut as LShift+RShift+ which I felt had a nice balance between deliberateness and easy-to-reach (since you are using it with your hands on homerow).

Though because some keyboards have key rollover issues with using both Shifts, Capslock+ is also allowed as an alternative activation shortcut.

[0] https://github.com/EsportToys/TPMouse

I personally use AutoIt a ton as a super fast way to quickly prototype GUIs. It's basically a really simple entrypoint for WinAPI.

Shameless plug: my script for emulating a trackball with your keyboard [0], and my tray app for quickly tweaking your cursor speed (usually for when I'm drawing something)[1]

  [0] https://github.com/EsportToys/TPMouse