Inputactions is no longer overriding the plasma default gestures

[tngstn]

I recently updated both plasma and inputactions (from like 2/3 months ago) and whereas inputactions used to completely block and take over the plasma touchpad baked-in gestures if you have the same trigger in your config, now both the plasma's gestures and inputactions' seem to be competing with each other.

In particular in my config I have 4 fingers swipe left/right to switch between tabs in the browser, that also happens to be the plasma gesture to switch between virtual desktops. So now when I 4 finger swipe half the time it switches virtual desktops instead of the brower tabs whereas inputactions used to have absolute priority.

Now I don't know it something has changed between 6.5 and 6.6 or something has changed in the inputaction code but it no longer seems to override plasma's gestures.

@taj-ny are you able to reproduce?

[taj-ny]

Diagonal swipe gestures were recently added, so what's probably happening is that you're swiping at an angle and it's getting detected as a diagonal swipe. I guess I'll disable them by default to prevent this issue from happening.

For now you could replace predefined directions with custom angle ranges (let me know if that solves the issue):

direction: left -> angle: 135-225
direction: right -> angle: 315-45
direction: up -> angle: 45-135
direction: down -> angle: 225-315

direction: up_down ->

angle: 225-315
bidirectional: true

direction: left_right ->

angle: 315-45
bidirectional: true

[tngstn]

Yes that was it, the gestures weren't detected if i was off-axis. I guess it's more noticable for the left/right gestures than the up/down ones. The custom angles fix works well.

Tysm for the quick response

[taj-ny]

I didn't want to disable diagonal directions by default so I added a way to set a custom global tolerance:

device_rules:
  - conditions: $touchpad
    swipe:
      angle_tolerance: 45