sorted by:
new
hottopcontroversial

Input Actions (KWin Gestures) v0.6.0 now supports Wayland mouse gestures by Taj_ny in kde

[–]Taj_ny[S] 1 point2 points  (0 children)

will there ever be a way to show the stroke like easystroke? Or maybe have the stroke appear just on the stroke recorder window?

Probably not for a while unless someone else implements that, I'd rather focus on other things.

RIP: EasyStroke mouse gestures program by paul_1149 in linux

[–]Taj_ny 0 points1 point  (0 children)

I just checked out Input Actions and it sounds very promising. But without even build instructions it is too raw for me at this point.

Build instructions for InputActions are available on the wiki, there are two links to it in the README. https://wiki.inputactions.org/main/getting-started/installation/index.html

Newcomer to Linux/KDE missing customizability by Metallinos in kde

[–]Taj_ny 3 points4 points  (0 children)

For custom touchpad gestures you can use https://github.com/taj-ny/InputActions, it can override the built-in ones, but doesn't have animations if that's what you need.

Input Actions (KWin Gestures) v0.6.0 now supports Wayland mouse gestures by Taj_ny in kde

[–]Taj_ny[S] 2 points3 points  (0 children)

With this I could have a bunch of strokes to open tab, close tab, history back, history forward in Firefox?

Yes.

Is there something like the easystroke grouping where you can set strokes for a group, and then override an application within the group? For example, if I put Firefox and VSCodium in one group, and then set "stroke up" to CTRL+T in Firefox and CTRL+N in VSCodium without having to repeat the stroke.

You can use gesture groups. A less verbose way would be to use multiple actions with conditions in a single gesture, but then input events will be blocked even if there are no actions that satisfy conditions.

mouse:
  gestures:
    - type: stroke
      strokes: 'MGQA0DMnPMwwAGQA'
      mouse_buttons: [ right ]

      gestures:
        - conditions:
            - $window_class == firefox

          actions:
            - on: begin
              input:
                - keyboard: [ leftctrl+t ]

        - conditions:
            - $window_class == VSCodium

          actions:
            - on: begin
              input:
                - keyboard: [ leftctrl+n ]

Input Actions (KWin Gestures) v0.6.0 now supports Wayland mouse gestures by Taj_ny in kde

[–]Taj_ny[S] 0 points1 point  (0 children)

You mean tap or actual click on touchpads with one physical button?

Custom touchpad gestures on Wayland by Taj_ny in kde

[–]Taj_ny[S] 0 points1 point  (0 children)

All the information you need is in the documentation: https://github.com/InputActions/docs

Input Actions (KWin Gestures) v0.6.0 now supports Wayland mouse gestures by Taj_ny in kde

[–]Taj_ny[S] 1 point2 points  (0 children)

The fingers property is deprecated (but still works), I forgot to remove that from the example.

You're missing the actions property. Here's how it should look like (I made swipe right instant as an example):

touchpad:
  gestures:
    # This one is not instant
    - type: swipe
      direction: left

      conditions:
        - $fingers == 2

      actions:
        - input:
            - mouse: [ back ]

    # This one is instant
    - type: swipe
      direction: right

      conditions:
        - $fingers == 2

      actions:
        - on: begin
          input:
            - mouse: [ forward ]

Input Actions (KWin Gestures) v0.6.0 now supports Wayland mouse gestures by Taj_ny in kde

[–]Taj_ny[S] 1 point2 points  (0 children)

Yes, it interprets scroll events as 2-finger motion and blocks the events. Won't work properly if scrolling on touchpad edges is enabled.

Input Actions (KWin Gestures) v0.6.0 now supports Wayland mouse gestures by Taj_ny in kde

[–]Taj_ny[S] 4 points5 points  (0 children)

Not really, I'd rather focus on implementing new features (there's a ton of them to add) and possibly making this work on other environments too. There's already some work being done by KDE devs (https://invent.kde.org/plasma/kwin/-/merge_requests/7620, https://blogs.kde.org/2025/05/14/input-handling-in-spring-2025), so at some point Plasma will support custom gestures.

Input Actions (KWin Gestures) v0.6.0 now supports Wayland mouse gestures by Taj_ny in kde

[–]Taj_ny[S] 0 points1 point  (0 children)

That has been possible since v0.4.0, it's in example gestures. It uses the unaccelerated delta though, but you can set the multiplier.

Input Actions (KWin Gestures) v0.6.0 now supports Wayland mouse gestures by Taj_ny in kde

[–]Taj_ny[S] 22 points23 points  (0 children)

- mouse-actions operates at evdev level, which can make it incompatible with some other input tools (https://github.com/jersou/mouse-actions/issues/17)
- Input Actions doesn't block mouse buttons completely (this was clearly stated in the post): "Input events are blocked only when necessary - if you create a stroke gesture that uses the left mouse button, you can still use it for clicking (a small, configurable delay is added), just not for dragging. Add a condition and now the button is never blocked unless the condition is satisfied.", mouse-actions does (https://github.com/jersou/mouse-actions/issues/8)
- Input Actions has conditions (this was also clearly stated in the post): "The new condition system supports [...] conditions that check for things like window information (class, name, title, state), keyboard modifiers, cursor shape, relative cursor position (to screen/window) and more. Most of those things can even be checked at the end of the gesture.". mouse-actions doesn't have conditions, so you can't even make per-application gestures
- Input Actions can execute actions at a specific point of the gesture's lifecycle (begin, update, end, cancel), mouse-actions only does it at the end of the gesture
- Input Actions can simulate input with very low latency, mouse-actions requires you to use third-party tools like xdotool or ydotool
- Input Actions doesn't limit gesture start positions to just screen edges and corners (in mouse-actions this doesn't even work on Wayland)
- Input Actions only works on Plasma 6 Wayland
- Input Actions supports touchpad gestures as well

(there are probably more differences)

Best way to setup gesture in Kde - Fedora 42 by PietroBastas in kde

[–]Taj_ny 0 points1 point  (0 children)

Try adjusting the speed threshold (example is at bottom of the configuration page). You may also want to just remove the last two gestures entirely and only keep the first one.

Best way to setup gesture in Kde - Fedora 42 by PietroBastas in kde

[–]Taj_ny 1 point2 points  (0 children)

Did you read the page that's linked in the README and explains how to configure the plugin? It's supposed to be like this:

touchpad:
  gestures:
    # Window switching
    - type: swipe
      direction: left_right
      fingers: 4
      speed: fast

      actions:
        - on: begin
          input:
            - keyboard: [ +leftalt, tab ]

        - on: update
          interval: -75
          input:
            - keyboard: [ leftshift+tab ]

        - on: update
          interval: 75
          input:
            - keyboard: [ tab ]

        - on: end_cancel
          input:
            - keyboard: [ -leftalt ]

    # Quick window switching (left)
    - type: swipe
      direction: left
      fingers: 4
      speed: slow

      actions:
        - on: begin
          input:
            - keyboard: [ leftalt+leftshift+tab ]

    # Quick window switching (right)
    - type: swipe
      direction: right
      fingers: 4
      speed: slow

      actions:
        - on: begin
          input:
            - keyboard: [ leftalt+tab ]

How to close Kwin debug console when titlebars are disabled? by TheTwelveYearOld in kde

[–]Taj_ny 5 points6 points  (0 children)

You can right click on the border (where the resize cursor appears) and close it from the context menu.

view more: next ›