Libinput Gestures Kde

broken image


  1. Libinput Gestures Kde Online
  2. Libinput Gestures Kde Na
  3. Libinput Gestures Kde Te
  4. Libinput Gestures Kde Je

If you want to set-up touchpad gestures on Linux, but don't know how, you should check out the following app.

The app is called ‘Gestures' and is described by its developer as being a 'minimal Gtk+ GUI app for libinput-gestures'.

Nov 29, 2020 I can't imagine how and why KDE would detect and report them in GUI without dedicated code on libinput-gestures side. How about I investigate the matter, and send a PR adding capability to send DBus notifications or show Qt/GTK dialogs? The number of users exposed to a -git version is probably minuscule after a week. For EWMH (see also wm-spec) compliant window managers, the libinput-gestures utility can be used meanwhile. The program reads libinput gestures (through libinput debug-events) from the touchpad and maps them to gestures according to a configuration file. Hence, it offers some flexibility within the boundaries of libinput's.

Windows and macOS both come with a variety of useful touchpad gestures pre-configured out of the box, and offer easy-to-access settings for adjusting or changing gesture behaviour to your liking.

Multi-touch touchpads are the standard these days. I searched around for good support, ideally out of the box, on modern Ubuntu. To be more specific: I'm on Kubuntu 20.04 without any relevant PPAs. Most solutions seem to involve libinput-gestures which, to be honest, is a super hacky solution. I use libinput-gestures for gestures on KDE with X11. It works pretty well, but it has to be configured from a file (instead of a native dialog), and sometimes it needs to be restarted when I resume from suspend. Multi-touch touchpads are the standard these days. I searched around for good support, ideally out of the box, on modern Ubuntu. To be more specific: I'm on Kubuntu 20.04 without any relevant PPAs. Most solutions seem to involve libinput-gestures which, to be honest, is a super hacky solution.

Alas Ubuntu, like many Linux distributions, is a little lacking in this regard. Only a handful of basic gestures for scrolling and right-click available out of the box on Ubuntu 18.04 LTS, for instance.

But by using the 'Gestures' app you can quickly effect a set of custom trackpad gestures that are on par with other operating systems, and in some cases, far more useful!

Create Touchpad Gestures on Ubuntu

Gestures provides an easy-to-use graphical front-end to libinput-gestures, thus saving you the need to craft a bespoke libinput-gestures config file by hand (or browse around to find a pre-prepared one online).

You can quickly enable trackpad gestures on Ubuntu 18.04 and similar Linux distributions, all based on whether you swipe or pinch the touchpad; the direction you move in; and/or the number of fingers you use in the gesture.

For instance, you could create a custom gesture to trigger the GNOME Shell Activities Overlay when you swipe down with two fingers (using xdtool to bind the gesture to a keyboard shortcut).

Libinput Gestures Kde Online

Kde

You might also set up a custom trackpad gesture with a four finger pinch instantly opening the Nautilus file manager, launch Firefox, take a screenshot, or anything else you want.

How to Get Gestures

You can learn more about Gestures over on its Gitlab page, linked below.

There you'll find a list of dependencies and build instructions for installing the app on your system: Screens 4 3 9 – access your computer remotely controls.

Reading this post from Solus? Lucky you, as Gestures is available from the Solus repos.

Libinput Gestures Kde Na

Thanks K. Renamer mac.

Thanks to the work done by Josè Expòsito, libinput 1.19 will ship with a new type of gesture: Hold Gestures. So far libinput supported swipe (moving multiple fingers in the same direction) and pinch (moving fingers towards each other or away from each other). These gestures are well-known, commonly used, and familiar to most users. For example, GNOME 40 recently has increased its use of touchpad gestures to switch between workspaces, etc. Swipe and pinch gestures require movement, it was not possible (for callers) to detect fingers on the touchpad that don't move.

This gap is now filled by Hold gestures. These are triggered when a user puts fingers down on the touchpad, without moving the fingers. This allows for some new interactions and we had two specific ones in mind: hold-to-click, a common interaction on older touchscreen interfaces where holding a finger in place eventually triggers the context menu. On a touchpad, a three-finger hold could zoom in, or do dictionary lookups, or kill a kitten. Whatever matches your user interface most, I guess.

The second interaction was the ability to stop kinetic scrolling. libinput does not actually provide kinetic scrolling, it merely provides the information needed in the client to do it there: specifically, it tells the caller when a finger was lifted off a touchpad at the end of a scroll movement. It's up to the caller (usually: the toolkit) to implement the kinetic scrolling effects. One missing piece was that while libinput provided information about lifting the fingers, it didn't provide information about putting fingers down again later - a common way to stop scrolling on other systems.

Libinput Gestures Kde Te

Strafe (2017). Hold gestures are intended to address this: a hold gesture triggered after a flick with two fingers can now be used by callers (read: toolkits) to stop scrolling.

Libinput Gestures Kde Je

Now, one important thing about hold gestures is that they will generate a lot of false positives, so be careful how you implement them. The vast majority of interactions with the touchpad will trigger some movement - once that movement hits a certain threshold the hold gesture will be cancelled and libinput sends out the movement events. Those events may be tiny (depending on touchpad sensitivity) so getting the balance right for the aforementioned hold-to-click gesture is up to the caller.

As usual, the required bits to get hold gestures into the wayland protocol are either in the works, mid-flight or merge-ready so expect this to hit the various repositories over the medium-term future.





broken image