New gesture system regressions

[non-bin]

I love the new gesture system (#11490) except for a few things:

No replacement for forever and direction_lock

workspace_swipe = true;
workspace_swipe_forever = true;
workspace_swipe_distance = 200;
workspace_swipe_direction_lock = false;

which becomes

gesture = 3, horizontal, scale: 2, workspace

but there is no equivalent to forever=true or direction_lock=false. Maybe we could add them as parameters like this?

gesture = 3, horizontal, scale: 2, workspace, forever: true, direction_lock: false

Configure delay before starting a gesture

Additionally, the gesture doesn't seem to start until I reach some speed, so I can't slowly switch workspaces, I have to flick a little to start the move.
It does make sense because we now have to account for more types of moves, but I feel like we could add something like gesture_min_velocity so tune that

No options for taps

I would like to bind a 4-finger tap to pause/play music, although maybe this would be better in the keybinds section

Add option to run a dispatcher every X units during a gesture

For example, to increase the volume every 20 units of movement or time:

gesture = 3, up, interval: 20, dispatcher, exec, wpctl set-volume @DEFAULT_AUDIO_SINK@ 5%+

and maybe even some placeholders like this:

%D - Direction: up down left right in out
%v - Velocity: units/second travelled in the last interval
%d - Distance: Total distance travelled since the start of the gesture
%t - Total/Displacement: Difference between start and current positions
%X %Y - Position relative to the gesture start position
%x %y - Movment since the last sample

Some examples:

• Use %D to change volume up or down with something like $([[ "%D" = "up" ]] && echo + || echo -)
• Use %x & %y to emulate an analog joystick (would be very useful for CAD)

[vaxerski]

forever and direction lock were not removed. They are still there....

Configure delay before starting a gesture

Not down to us. That's down to your touchpad's driver.

No options for taps

Not a thing AFAIK under libinput.

Add option to run a dispatcher every X units during a gesture

Already reported elsweyr

[non-bin]

forever and direction lock were not removed. They are still there....

Sorry I assumed they were removed for some reason :P

Not down to us. That's down to your touchpad's driver.

How did the old gestures work? They started as soon as you put down the 3rd finger

Not a thing AFAIK under libinput.

I don't think that's true. libinput reports every raw touch, it's up to aquamarine and hyprland to decide what to do with it. For example a 5 finger tap reports the position of each finger by its ABS_MT_SLOT, just like it would with the gestures. It would be harder than just reading for left/middle/right buttons, but possible.

$ sudo libinput record
[...]
- evdev:
    - [  0,      0,   3,  47,       0] # EV_ABS / ABS_MT_SLOT               0
    - [  0,      0,   3,  57,    2939] # EV_ABS / ABS_MT_TRACKING_ID     2939
    - [  0,      0,   3,  53,    2995] # EV_ABS / ABS_MT_POSITION_X      2995 (+169)
    - [  0,      0,   3,  54,     834] # EV_ABS / ABS_MT_POSITION_Y       834 (+33)
    - [  0,      0,   3,  47,       1] # EV_ABS / ABS_MT_SLOT               1
    - [  0,      0,   3,  57,    2940] # EV_ABS / ABS_MT_TRACKING_ID     2940
    - [  0,      0,   3,  53,     750] # EV_ABS / ABS_MT_POSITION_X       750 (-2675)
    - [  0,      0,   3,  54,    1791] # EV_ABS / ABS_MT_POSITION_Y      1791 (+951)
    - [  0,      0,   1, 330,       1] # EV_KEY / BTN_TOUCH                 1
    - [  0,      0,   1, 333,       1] # EV_KEY / BTN_TOOL_DOUBLETAP        1
    - [  0,      0,   3,   0,    2995] # EV_ABS / ABS_X                  2995 (+169)
    - [  0,      0,   3,   1,     834] # EV_ABS / ABS_Y                   834 (+33)
    - [  0,      0,   4,   5,       0] # EV_MSC / MSC_TIMESTAMP             0
    - [  0,      0,   0,   0,       0] # ------------ SYN_REPORT (0) ---------- +0ms
  - evdev:
    - [  0,   5675,   3,  47,       2] # EV_ABS / ABS_MT_SLOT               2
    - [  0,   5675,   3,  57,    2941] # EV_ABS / ABS_MT_TRACKING_ID     2941
    - [  0,   5675,   3,  53,    1732] # EV_ABS / ABS_MT_POSITION_X      1732 (-761)
    - [  0,   5675,   3,  54,     165] # EV_ABS / ABS_MT_POSITION_Y       165 (-688)
    - [  0,   5675,   3,  47,       3] # EV_ABS / ABS_MT_SLOT               3
    - [  0,   5675,   3,  57,    2942] # EV_ABS / ABS_MT_TRACKING_ID     2942
    - [  0,   5675,   3,  53,    2341] # EV_ABS / ABS_MT_POSITION_X      2341 (-981)
    - [  0,   5675,   3,  54,     394] # EV_ABS / ABS_MT_POSITION_Y       394 (-669)
    - [  0,   5675,   3,  47,       4] # EV_ABS / ABS_MT_SLOT               4
    - [  0,   5675,   3,  57,    2943] # EV_ABS / ABS_MT_TRACKING_ID     2943
    - [  0,   5675,   3,  53,    1072] # EV_ABS / ABS_MT_POSITION_X      1072 (+1072)
    - [  0,   5675,   3,  54,     743] # EV_ABS / ABS_MT_POSITION_Y       743 (+743)
    - [  0,   5675,   1, 333,       0] # EV_KEY / BTN_TOOL_DOUBLETAP        0
    - [  0,   5675,   1, 328,       1] # EV_KEY / BTN_TOOL_QUINTTAP         1
    - [  0,   5675,   4,   5,    7700] # EV_MSC / MSC_TIMESTAMP          7700
    - [  0,   5675,   0,   0,       0] # ------------ SYN_REPORT (0) ---------- +
[...]

[vaxerski]

I don't think that's true. libinput reports every raw touch, it's up to aquamarine and hyprland to decide what to do with it. For example a 5 finger tap reports the position of each finger by its ABS_MT_SLOT, just like it would with the gestures. It would be harder than just reading for left/middle/right buttons, but possible.

Well that's why I said AFAIK. I did not make libinput. Cool, so that is a thing, I'll reference that under #11724

How did the old gestures work? They started as soon as you put down the 3rd finger

Well that's odd. We only wait for a very small delta to determine the direction in the beginning, 5 device pixels. On most devices, that's like... a millimeter.

We can't "immediately" start because you might get tiny movements up/down and then swipe left (we're humans) and we don't want to lock you in prematurely.

[non-bin]

Well that's odd. We only wait for a very small delta to determine the direction in the beginning, 5 device pixels. On most devices, that's like... a millimeter.

Experimentally it seems to be a speed that it waits for, I can move across the entire trackpad if I stay under about 1cm/s, when I go above that the gesture starts

[vaxerski]

oh no you are right.

[vaxerski]

#11851

[steelpancake]

Also, I don't see a way to get the workspace_swipe_use_r functionality back. Its the one where if you swipe from workspace 1, and workspace two is empty and workspace 3 is not, it still swipes to workspace 2 instead of skipping over it

[vaxerski]

its still there bro