New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Touchpad Settings (Request) #92

Open
intialonso opened this Issue May 10, 2014 · 24 comments

Comments

@intialonso

intialonso commented May 10, 2014

This is more a request than a bug.

In the mouse settings theres no options for touchpads (vertical and horizontal scroll, tap, etc). It will be great if the option could be included in the settings app.

@jleclanche

This comment has been minimized.

Show comment
Hide comment
@jleclanche

jleclanche May 11, 2014

Contributor

Accepted

Contributor

jleclanche commented May 11, 2014

Accepted

@fedelibre

This comment has been minimized.

Show comment
Hide comment
@fedelibre

fedelibre Jul 12, 2015

+1, this would be very nice to have

fedelibre commented Jul 12, 2015

+1, this would be very nice to have

@PCMan

This comment has been minimized.

Show comment
Hide comment
@PCMan

PCMan Jul 13, 2015

Member

Does anyone know how to do that?

Member

PCMan commented Jul 13, 2015

Does anyone know how to do that?

@fedelibre

This comment has been minimized.

Show comment
Hide comment
@fedelibre

fedelibre Jul 13, 2015

perhaps you can get some ispiration from gnome-control-center

fedelibre commented Jul 13, 2015

perhaps you can get some ispiration from gnome-control-center

@Vladimir-csp

This comment has been minimized.

Show comment
Hide comment
@Vladimir-csp

Vladimir-csp Jul 13, 2015

A humble request: while taking ideas from gnome stuff, try to avoid oversimplification. Some time ago I've tried to convince them to make decent mouse speed and acceleration settings. In the end they changed two non-working sliders into one which does magic with no way to tell where speed setting ends and acceleration setting begins.

Vladimir-csp commented Jul 13, 2015

A humble request: while taking ideas from gnome stuff, try to avoid oversimplification. Some time ago I've tried to convince them to make decent mouse speed and acceleration settings. In the end they changed two non-working sliders into one which does magic with no way to tell where speed setting ends and acceleration setting begins.

@jleclanche

This comment has been minimized.

Show comment
Hide comment
@jleclanche

jleclanche Jul 13, 2015

Contributor

@Vladimir-csp When making UX decisions I try to make the interface as simple as possible without removing actual functionality.

Contributor

jleclanche commented Jul 13, 2015

@Vladimir-csp When making UX decisions I try to make the interface as simple as possible without removing actual functionality.

@Atalanttore

This comment has been minimized.

Show comment
Hide comment
@Atalanttore

Atalanttore Aug 3, 2015

Can you please turn off tapping by default? It's annoying and unnecessary.

Atalanttore commented Aug 3, 2015

Can you please turn off tapping by default? It's annoying and unnecessary.

@Vladimir-csp

This comment has been minimized.

Show comment
Hide comment
@Vladimir-csp

Vladimir-csp Nov 4, 2015

Touchpad settings are usually just xinput properties of the device. No need for any special treatment. IMHO this should be merged into #337

Vladimir-csp commented Nov 4, 2015

Touchpad settings are usually just xinput properties of the device. No need for any special treatment. IMHO this should be merged into #337

@RalfJung

This comment has been minimized.

Show comment
Hide comment
@RalfJung

RalfJung Mar 20, 2016

Is there any other configuration tool one could use? I tried the one from GNOME, but enabling "tap to click" there does nothing. I tried the one from KDE, but so far I was unable to even load it:

$ kcmshell5 kcm_touchpad
"kcm_touchpad" should not be loaded.
Could not find module 'kcm_touchpad'. See kcmshell5 --list for the full list of modules.

Not being able to tap to click is a pretty severe regression, compared to the DEs I used previously.

EDIT: I solved this for now by editing the Xorg configuration. Better than nothing.

RalfJung commented Mar 20, 2016

Is there any other configuration tool one could use? I tried the one from GNOME, but enabling "tap to click" there does nothing. I tried the one from KDE, but so far I was unable to even load it:

$ kcmshell5 kcm_touchpad
"kcm_touchpad" should not be loaded.
Could not find module 'kcm_touchpad'. See kcmshell5 --list for the full list of modules.

Not being able to tap to click is a pretty severe regression, compared to the DEs I used previously.

EDIT: I solved this for now by editing the Xorg configuration. Better than nothing.

@palinek

This comment has been minimized.

Show comment
Hide comment
@palinek

palinek Mar 21, 2016

Contributor

There is a synclient cmd line tool for the synaptics. Do we want to make a GUI based on that? (like it is with setxkbmap in lxqt-config-input)

Contributor

palinek commented Mar 21, 2016

There is a synclient cmd line tool for the synaptics. Do we want to make a GUI based on that? (like it is with setxkbmap in lxqt-config-input)

@Vladimir-csp

This comment has been minimized.

Show comment
Hide comment
@Vladimir-csp

Vladimir-csp Mar 21, 2016

There is a synclient cmd line tool for the synaptics. Do we want to make a GUI based on that? (like it is with setxkbmap in lxqt-config-input)

IMHO, not before proper xinput frontend/daemon (#337).

...some of touchpad properties are exposed via xinput anyway.

Vladimir-csp commented Mar 21, 2016

There is a synclient cmd line tool for the synaptics. Do we want to make a GUI based on that? (like it is with setxkbmap in lxqt-config-input)

IMHO, not before proper xinput frontend/daemon (#337).

...some of touchpad properties are exposed via xinput anyway.

@pmattern

This comment has been minimized.

Show comment
Hide comment
@pmattern

pmattern Mar 21, 2016

Contributor

Tools synclient as well as syndaemon are geared towards xf86-input-synaptics only. They don't work with any other driver like e. g. xf86-input-libinput so we shouldn't rely on them.

AFAIK the common way to tweak input device settings in realtime are Device Properties so we'd better use these as backend.
Don't know whether this has to be done via binary xinput or whether there's some library or so to access them. Also, I'm not sure which Device Properties exactly should be supported as these are completely different depending on the driver in use. libinput will probably be used under Wayland as well, synaptics is providing a lot more features for the time being, supporting both would probably mean much more work.

Also, I don't know how that whole thing will be implemented in Wayland, in particular whether the concept of Device Properties will persist.
If Wayland is relying on different concepts I'm not sure whether effort should be put into the current X Window System concepts, besides a GUI to configure touchpads is for sure a feature missing badly.

Contributor

pmattern commented Mar 21, 2016

Tools synclient as well as syndaemon are geared towards xf86-input-synaptics only. They don't work with any other driver like e. g. xf86-input-libinput so we shouldn't rely on them.

AFAIK the common way to tweak input device settings in realtime are Device Properties so we'd better use these as backend.
Don't know whether this has to be done via binary xinput or whether there's some library or so to access them. Also, I'm not sure which Device Properties exactly should be supported as these are completely different depending on the driver in use. libinput will probably be used under Wayland as well, synaptics is providing a lot more features for the time being, supporting both would probably mean much more work.

Also, I don't know how that whole thing will be implemented in Wayland, in particular whether the concept of Device Properties will persist.
If Wayland is relying on different concepts I'm not sure whether effort should be put into the current X Window System concepts, besides a GUI to configure touchpads is for sure a feature missing badly.

@Vladimir-csp

This comment has been minimized.

Show comment
Hide comment
@Vladimir-csp

Vladimir-csp Mar 21, 2016

Breaking it apart: there is a need for input device configuration tool. This tool would work with a range of properties, grouped in profiles which would be applied to devices.

It would be logical to generalize properties and create a list of known properties with (translatable) descriptions.

The config tool would take a list of available properties, compare it to a list of known properties, then show known ones on the 'main' tab, all other on 'advanced' tab.

Where would it take all these properties? That depends on backends. Wayland is maturing, but it is still not mainstream, nor has stable interfaces. So xinput is the thing to start with (via binary or library, does not matter).

The plus side of this approach is that it would provide GUI access to any property backend can give. In case of xinput it is very impressive list, sufficient to handle a touchpad:

$ xinput list-props 14
Device 'AlpsPS/2 ALPS GlidePoint':
    Device Enabled (137):   1
    Coordinate Transformation Matrix (139): 1.000000, 0.000000, 0.000000, 0.000000, 1.000000, 0.000000, 0.000000, 0.000000, 1.000000
    Device Accel Profile (270): -1
    Device Accel Constant Deceleration (271):   2.500000
    Device Accel Adaptive Deceleration (272):   1.000000
    Device Accel Velocity Scaling (273):    12.500000
    Synaptics Edges (294):  300, 1700, 210, 1190
    Synaptics Finger (295): 12, 15, 0
    Synaptics Tap Time (296):   180
    Synaptics Tap Move (297):   107
    Synaptics Tap Durations (298):  180, 100, 100
    Synaptics ClickPad (299):   0
    Synaptics Middle Button Timeout (300):  75
    Synaptics Two-Finger Pressure (301):    141
    Synaptics Two-Finger Width (302):   7
    Synaptics Scrolling Distance (303): 48, 48
    Synaptics Edge Scrolling (304): 0, 0, 0
    Synaptics Two-Finger Scrolling (305):   1, 1
    Synaptics Move Speed (306): 1.000000, 1.750000, 0.081934, 0.000000
    Synaptics Off (307):    0
    Synaptics Locked Drags (308):   0
    Synaptics Locked Drags Timeout (309):   5000
    Synaptics Tap Action (310): 0, 0, 0, 0, 1, 2, 3
    Synaptics Click Action (311):   1, 1, 1
    Synaptics Circular Scrolling (312): 0
    Synaptics Circular Scrolling Distance (313):    0.100000
    Synaptics Circular Scrolling Trigger (314): 0
    Synaptics Circular Pad (315):   0
    Synaptics Palm Detection (316): 0
    Synaptics Palm Dimensions (317):    10, 100
    Synaptics Coasting Speed (318): 20.000000, 50.000000
    Synaptics Pressure Motion (319):    15, 80
    Synaptics Pressure Motion Factor (320): 1.000000, 1.000000
    Synaptics Grab Event Device (321):  0
    Synaptics Gestures (322):   1
    Synaptics Capabilities (323):   1, 1, 1, 1, 1, 1, 0
    Synaptics Pad Resolution (324): 32, 25
    Synaptics Area (325):   0, 0, 0, 0
    Synaptics Noise Cancellation (326): 12, 12
    Device Product ID (260):    2, 8
    Device Node (261):  "/dev/input/event1"

Everything I wrote here is just a clarification of the concept already described in #337

Vladimir-csp commented Mar 21, 2016

Breaking it apart: there is a need for input device configuration tool. This tool would work with a range of properties, grouped in profiles which would be applied to devices.

It would be logical to generalize properties and create a list of known properties with (translatable) descriptions.

The config tool would take a list of available properties, compare it to a list of known properties, then show known ones on the 'main' tab, all other on 'advanced' tab.

Where would it take all these properties? That depends on backends. Wayland is maturing, but it is still not mainstream, nor has stable interfaces. So xinput is the thing to start with (via binary or library, does not matter).

The plus side of this approach is that it would provide GUI access to any property backend can give. In case of xinput it is very impressive list, sufficient to handle a touchpad:

$ xinput list-props 14
Device 'AlpsPS/2 ALPS GlidePoint':
    Device Enabled (137):   1
    Coordinate Transformation Matrix (139): 1.000000, 0.000000, 0.000000, 0.000000, 1.000000, 0.000000, 0.000000, 0.000000, 1.000000
    Device Accel Profile (270): -1
    Device Accel Constant Deceleration (271):   2.500000
    Device Accel Adaptive Deceleration (272):   1.000000
    Device Accel Velocity Scaling (273):    12.500000
    Synaptics Edges (294):  300, 1700, 210, 1190
    Synaptics Finger (295): 12, 15, 0
    Synaptics Tap Time (296):   180
    Synaptics Tap Move (297):   107
    Synaptics Tap Durations (298):  180, 100, 100
    Synaptics ClickPad (299):   0
    Synaptics Middle Button Timeout (300):  75
    Synaptics Two-Finger Pressure (301):    141
    Synaptics Two-Finger Width (302):   7
    Synaptics Scrolling Distance (303): 48, 48
    Synaptics Edge Scrolling (304): 0, 0, 0
    Synaptics Two-Finger Scrolling (305):   1, 1
    Synaptics Move Speed (306): 1.000000, 1.750000, 0.081934, 0.000000
    Synaptics Off (307):    0
    Synaptics Locked Drags (308):   0
    Synaptics Locked Drags Timeout (309):   5000
    Synaptics Tap Action (310): 0, 0, 0, 0, 1, 2, 3
    Synaptics Click Action (311):   1, 1, 1
    Synaptics Circular Scrolling (312): 0
    Synaptics Circular Scrolling Distance (313):    0.100000
    Synaptics Circular Scrolling Trigger (314): 0
    Synaptics Circular Pad (315):   0
    Synaptics Palm Detection (316): 0
    Synaptics Palm Dimensions (317):    10, 100
    Synaptics Coasting Speed (318): 20.000000, 50.000000
    Synaptics Pressure Motion (319):    15, 80
    Synaptics Pressure Motion Factor (320): 1.000000, 1.000000
    Synaptics Grab Event Device (321):  0
    Synaptics Gestures (322):   1
    Synaptics Capabilities (323):   1, 1, 1, 1, 1, 1, 0
    Synaptics Pad Resolution (324): 32, 25
    Synaptics Area (325):   0, 0, 0, 0
    Synaptics Noise Cancellation (326): 12, 12
    Device Product ID (260):    2, 8
    Device Node (261):  "/dev/input/event1"

Everything I wrote here is just a clarification of the concept already described in #337

@billwx

This comment has been minimized.

Show comment
Hide comment
@billwx

billwx May 9, 2016

Not sure if this is helpful but xfce recognizes both my laptop and usb mice. I always disable the former to avoid accidentally moving my cursor about when typing. With lxde/qt i have to be much more careful about not touching the trackpad. Such an option would be a great addition to a great desktop. Thanks for your consideration!

billwx commented May 9, 2016

Not sure if this is helpful but xfce recognizes both my laptop and usb mice. I always disable the former to avoid accidentally moving my cursor about when typing. With lxde/qt i have to be much more careful about not touching the trackpad. Such an option would be a great addition to a great desktop. Thanks for your consideration!

@tsujan

This comment has been minimized.

Show comment
Hide comment
@tsujan

tsujan May 9, 2016

Member

With lxde/qt i have to be much more careful about not touching the trackpad

Until that option is added, if your touchpad works with Synaptics driver, you could add this to your startup:

#!/bin/bash
synclient TouchpadOff=1
exit

or to keyboard shortcuts.

Member

tsujan commented May 9, 2016

With lxde/qt i have to be much more careful about not touching the trackpad

Until that option is added, if your touchpad works with Synaptics driver, you could add this to your startup:

#!/bin/bash
synclient TouchpadOff=1
exit

or to keyboard shortcuts.

@josephg5

This comment has been minimized.

Show comment
Hide comment
@josephg5

josephg5 Aug 6, 2016

with xinput

$ xinput --list
$ xinput --list-props "SynPS/2 Synaptics TouchPad"

$ xinput --set-prop "SynPS/2 Synaptics TouchPad" "libinput Tapping Enabled" 1

josephg5 commented Aug 6, 2016

with xinput

$ xinput --list
$ xinput --list-props "SynPS/2 Synaptics TouchPad"

$ xinput --set-prop "SynPS/2 Synaptics TouchPad" "libinput Tapping Enabled" 1

@billwx

This comment has been minimized.

Show comment
Hide comment
@billwx

billwx Aug 19, 2016

On my Dell Latitude e5420 running the latest (arch-based) Antergos and LxQt, xinput says unable to find SynPS/2 Synaptics TouchPad. ANy further advice? Is it possible my machine is using a different touchpad? Many thanks!


From: Joseph George notifications@github.com
Sent: Saturday, August 6, 2016 4:30 PM
To: lxde/lxqt
Cc: billwx; Comment
Subject: Re: [lxde/lxqt] Touchpad Settings (Request) (#92)

with xinput

$ xinput --list
$ xinput --list-props "SynPS/2 Synaptics TouchPad"

$ xinput --set-prop "SynPS/2 Synaptics TouchPad" "libinput Tapping Enabled" 1

You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://github.com/lxde/lxqt/issues/92#issuecomment-238049764, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ASXqHGUcH_hUqPVRXRhS-sUyGkgFueHVks5qdPzjgaJpZM4B5ysj.

billwx commented Aug 19, 2016

On my Dell Latitude e5420 running the latest (arch-based) Antergos and LxQt, xinput says unable to find SynPS/2 Synaptics TouchPad. ANy further advice? Is it possible my machine is using a different touchpad? Many thanks!


From: Joseph George notifications@github.com
Sent: Saturday, August 6, 2016 4:30 PM
To: lxde/lxqt
Cc: billwx; Comment
Subject: Re: [lxde/lxqt] Touchpad Settings (Request) (#92)

with xinput

$ xinput --list
$ xinput --list-props "SynPS/2 Synaptics TouchPad"

$ xinput --set-prop "SynPS/2 Synaptics TouchPad" "libinput Tapping Enabled" 1

You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://github.com/lxde/lxqt/issues/92#issuecomment-238049764, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ASXqHGUcH_hUqPVRXRhS-sUyGkgFueHVks5qdPzjgaJpZM4B5ysj.

@stefonarch

This comment has been minimized.

Show comment
Hide comment
@stefonarch

stefonarch Aug 19, 2016

Sometimes non-synaptis touchpads are recognised only as mouse, you can see the model with
$ xinput list

Better you search on the net specific solutions for your laptop model, it's not related in any way to LQXt.

stefonarch commented Aug 19, 2016

Sometimes non-synaptis touchpads are recognised only as mouse, you can see the model with
$ xinput list

Better you search on the net specific solutions for your laptop model, it's not related in any way to LQXt.

@billwx

This comment has been minimized.

Show comment
Hide comment
@billwx

billwx Aug 22, 2016

I respectfully disagree. Certainly the way to disable a trackpad is related to one's operating system?

However, thank you for the tip on "xinput list". Using that command,and previous instructions from Joseph George, i disabled the trackpad on my Dell Latitude e5420 by...

xinput --set-prop "AlpsPS/2 ALPS GlidePoint" "Device Enabled" 0


From: Stefano Binde notifications@github.com
Sent: Friday, August 19, 2016 9:58 AM
To: lxde/lxqt
Cc: billwx; Comment
Subject: Re: [lxde/lxqt] Touchpad Settings (Request) (#92)

Sometimes non-synaptis touchpads are recognised only as mouse, you can see the model with
$ xinput list

Better you search on the net specific solutions for your laptop model, it's not related in any way to LQXt.

You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://github.com/lxde/lxqt/issues/92#issuecomment-241041934, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ASXqHA1jyjb_4kW-VZ4rOHuVw5iQjUB4ks5qhcSpgaJpZM4B5ysj.

billwx commented Aug 22, 2016

I respectfully disagree. Certainly the way to disable a trackpad is related to one's operating system?

However, thank you for the tip on "xinput list". Using that command,and previous instructions from Joseph George, i disabled the trackpad on my Dell Latitude e5420 by...

xinput --set-prop "AlpsPS/2 ALPS GlidePoint" "Device Enabled" 0


From: Stefano Binde notifications@github.com
Sent: Friday, August 19, 2016 9:58 AM
To: lxde/lxqt
Cc: billwx; Comment
Subject: Re: [lxde/lxqt] Touchpad Settings (Request) (#92)

Sometimes non-synaptis touchpads are recognised only as mouse, you can see the model with
$ xinput list

Better you search on the net specific solutions for your laptop model, it's not related in any way to LQXt.

You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://github.com/lxde/lxqt/issues/92#issuecomment-241041934, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ASXqHA1jyjb_4kW-VZ4rOHuVw5iQjUB4ks5qhcSpgaJpZM4B5ysj.

@stefonarch

This comment has been minimized.

Show comment
Hide comment
@stefonarch

stefonarch Aug 22, 2016

I respectfully disagree. Certainly the way to disable a trackpad is related to one's operating system?

Yes, but in case the trackpad is not recognised by the kernel there is no DE which makes miracles.

stefonarch commented Aug 22, 2016

I respectfully disagree. Certainly the way to disable a trackpad is related to one's operating system?

Yes, but in case the trackpad is not recognised by the kernel there is no DE which makes miracles.

@yan12125

This comment has been minimized.

Show comment
Hide comment
@yan12125

yan12125 Nov 7, 2016

Member

Following the idea of @josephg5 and description on https://bbs.archlinux.org/viewtopic.php?id=210096, this is how I change my scrolling method to edge-scrolling:

xinput --set-prop "ETPS/2 Elantech Touchpad" "libinput Scroll Method Enabled" 0, 1, 0

libinput provides some configuration APIs, which seems promising: https://wayland.freedesktop.org/libinput/doc/latest/group__config.html

Member

yan12125 commented Nov 7, 2016

Following the idea of @josephg5 and description on https://bbs.archlinux.org/viewtopic.php?id=210096, this is how I change my scrolling method to edge-scrolling:

xinput --set-prop "ETPS/2 Elantech Touchpad" "libinput Scroll Method Enabled" 0, 1, 0

libinput provides some configuration APIs, which seems promising: https://wayland.freedesktop.org/libinput/doc/latest/group__config.html

@yan12125

This comment has been minimized.

Show comment
Hide comment
@yan12125

yan12125 Nov 12, 2016

Member

In response to @fedelibre:

perhaps you can get some ispiration from gnome-control-center

In brief: X11-specific codes seem inevitable for implementing this

Take tap-to-click for eample: gnome-control-center sends configurations to gnome-settings-daemon (gsd) [1]. On the other hand, mutter subscribes the setting from gsd [2]. Mutter then sends an X11 Atom to Xorg server to change the setting. [3]

(PS. I'm new to GTK+/GLib. The conclusion above is from 2-hour reading of GNOME codes, which may be wrong)

libinput settings are context-wise. That is, settings in a process are independent from another process. As a result, for LXQt running on Xorg, lxqt-config needs to use the X protocol to change those settings. That's a bad news for a desktop environment aiming to support wayland.

[1] https://git.gnome.org/browse/gnome-control-center/tree/panels/mouse/gnome-mouse-properties.c#n285
[2] https://git.gnome.org/browse/mutter/tree/src/backends/meta-input-settings.c#n457
[3] https://git.gnome.org/browse/mutter/tree/src/backends/x11/meta-input-settings-x11.c#n214

Member

yan12125 commented Nov 12, 2016

In response to @fedelibre:

perhaps you can get some ispiration from gnome-control-center

In brief: X11-specific codes seem inevitable for implementing this

Take tap-to-click for eample: gnome-control-center sends configurations to gnome-settings-daemon (gsd) [1]. On the other hand, mutter subscribes the setting from gsd [2]. Mutter then sends an X11 Atom to Xorg server to change the setting. [3]

(PS. I'm new to GTK+/GLib. The conclusion above is from 2-hour reading of GNOME codes, which may be wrong)

libinput settings are context-wise. That is, settings in a process are independent from another process. As a result, for LXQt running on Xorg, lxqt-config needs to use the X protocol to change those settings. That's a bad news for a desktop environment aiming to support wayland.

[1] https://git.gnome.org/browse/gnome-control-center/tree/panels/mouse/gnome-mouse-properties.c#n285
[2] https://git.gnome.org/browse/mutter/tree/src/backends/meta-input-settings.c#n457
[3] https://git.gnome.org/browse/mutter/tree/src/backends/x11/meta-input-settings-x11.c#n214

@yan12125

This comment has been minimized.

Show comment
Hide comment
@yan12125

yan12125 Dec 1, 2016

Member

I have a quick implementation at lxqt/lxqt-config#109. Hope everyone can have a test as it's highly hardware-dependent and I'm not sure if things are still working with different configurations.

Member

yan12125 commented Dec 1, 2016

I have a quick implementation at lxqt/lxqt-config#109. Hope everyone can have a test as it's highly hardware-dependent and I'm not sure if things are still working with different configurations.

@Luraktinus

This comment has been minimized.

Show comment
Hide comment
@Luraktinus

Luraktinus Feb 25, 2018

i wanna see that too, the buttons on my touchpad are broken and barely work... tapping is the only way for me (also its way more comfy)

Luraktinus commented Feb 25, 2018

i wanna see that too, the buttons on my touchpad are broken and barely work... tapping is the only way for me (also its way more comfy)

@agaida agaida added this to Needs triage in Issues Jul 14, 2018

@agaida agaida moved this from Needs triage to Low priority in Issues Jul 15, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment