TPMouse VS xdo

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

An example with xdo:

I might have understood your question wrong, if you want to close the GUI window after staring the app you'd want to take a look at xdo. I'd still give it a little bit of time after starting it to be ready and then use something like:

xdo (by baskerville, bspwm's creator);

The focusonnetactive patch replaces dwm's default behavior by removing the urgency bit to allow for focusing on the client sending the _NET_ACTIVE_WINDOW message instead. This is the preferred behavior if you use tools like xdo to perform actions on windows, for example: