temporary speed change about warpd HOT 9 CLOSED

Again I'm very late with a reply, sorry for this. The acceleration feature works like a charm (as was to be expected) and I'm actually using it quite often. Thanks again, I really can't stress enough how useful warp/keyd are for me! They solved all the input problems I had been struggling with for years, and the longer I use them, the more I get the impression that all the feature requests I'm posting here are just desperate attempts to convince myself that there can't be software which is almost perfect (another such attempt is my inclusion of the word 'almost').

from warpd.

I second this.

from warpd.

I've been meaning to add configurable pointer acceleration to account for the gap between macoscopic and fine movement. I'm not opposed to also adding some kind of explicit speed toggle, but I wonder if the former might be sufficient.

from warpd.

To make this solution feature complete, there should also be kinetic movement (as present in trackpoint hardware as well as qmk and uhk), so that as soon as a movement key is pressed the pointer gets accelerated according to some quadratic curve. Short presses thus cause slow and precise movements while longer presses can cover distances. However, as this is probably a bit involved, I suggested incorporating full mouse control in keyd, see my other comment at rvaiya/keyd#158

from warpd.

so that as soon as a movement key is pressed the pointer gets accelerated according to some quadratic curve

Indeed. This is what I meant by 'pointer acceleration'. There is already similar logic for scrolling (scroll velocity increases with time). The older version even had something called 'scroll flinging' which was fully inertial scrolling to which you could impart an impulse by tapping the scroll key for a second or third time, but I ended up removing it after realizing it wasn't very useful for most scrolling tasks, and probably counter productive in most cases.

from warpd.

Pointer acceleration is now enabled by default in the latest release. I've picked defaults which feel reasonable on my machine, but you may want to play with the acceleration and max_speed variables. If you still feel the need for dedicated keys after using this for a bit let me know :).

Edit:

You may also want to adjust some of your other config values, as the default pixel size has changed.

from warpd.

Thank you very much, have been using it for about a week now and it works like a charm! On my trackpoint-less keyboards I still miss a “quick move” possibility (for covering mid-range distances for which a hint-mode jump would take too long) but this is definitely not urgent, nor critical. If you decide and find the time to implement it: How about a generic action, which would disable acceleration and sets speed to a given argument while the corresponding activation key is held down? This way one could either slow down or speed up movement.
Another option would be to just multiply speed, acceleration and max_speed by some factor, but this seems less useful to me.

from warpd.

I've added an acceleration key to the latest commit which changes the acceleration while held, though I personally haven't found it very useful. I've found that with the right acceleration/speed values short-midrange movement is best achieved without any modifiers and hint mode is still more efficient for longer distances.

from warpd.

I'm closing this for now. Feel free to reopen it if you feel the issue is unresolved.

from warpd.