LXQt 0.14 introduced more fine-tuned touchpad support. We should have some sane default settings for it.
|Open||None||T157 Unassigned tasks or without scope|
|Upstream||None||T26 Define and Implement Default Settings for Touchpad|
I violently loathe tap to click. However, I know it is often requested and is something you find on Windows machines by default (but not Macs, I might add), so I can live with it.
- Natural scrolling should, most certainly, remain off. Every time I touch a modern Mac, it makes me want to throw it across the room.
- Tap to drag seems confusing to me if we also have tap to click.
- I'm a *huge* fan of two finger scrolling and don't know what I'd do without it. I actually use it for horizontal and vertical, too.
I understand that all that is already on default. It would be good to test it, needs to be on bare metal.
Or should we also put that as our own default in case upstream changes it?
I like explicit configurations as there's no question as to what the default is and whether or not it matches expectations.
Also re: our IRC discussion, we need a libinput-compatible solution, as D1: Set tap to click as default for touchpad seems to only support synaptics, at least judging by the name of the configuration option. libinput should support essentially everything that's not bleeding edge. synaptics is basically in "maintenance mode" which is to say it's deprecated. The author/maintainer of libinput is the author/maintainer of synaptics, so when I say it's dropped, it's dropped.
Actually looking at an answer on AskUbuntu it may be possible, at least through Xorg. There must be a way.
I wonder as well.
It is true that the code sets the libinput status but it also looks at touchpads dynamically which treats each touchpad attached separately. If we start messing with it I wonder what will happen.
I do think that pointers and touchpads are separate as far as libinput is concerned. We don't have to be *that* device-agnostic as long as we don't have to do specific things for each specific device. That seems contrary to the whole point of libinput.
@hmollercl the problem is that your settings will not work for every device. They're too specific.
You know we should look at this upstream patch before delving in too deep on this. Can someone try to apply the patch?
This is a good idea, but it's not something we can adequately control yet. All settings are specific to a particular device. There's no way to refer to pointing devices in general. There is some discussion about ways to implement this but it's uncertain.
Maybe next release. :/