tag:blogger.com,1999:blog-6112936277054198647.post2071610686466346506..comments2024-03-12T00:42:06.642+10:00Comments on Who-T: Why libinput doesn't have a lot of config optionsPeter Huttererhttp://www.blogger.com/profile/17204066043271384535noreply@blogger.comBlogger8125tag:blogger.com,1999:blog-6112936277054198647.post-42605271705514738252016-05-05T07:26:13.621+10:002016-05-05T07:26:13.621+10:00Hi,
Not sure if that' the right place to ask ...Hi,<br /><br />Not sure if that' the right place to ask this question,<br />but it feels relevant enough ;)<br /><br />I have always used left wheel tilt as a middle button (by switching<br />those two "buttons" using "ButtonMapping" in xorg configuration file).<br />I did that because the regular middle button on most mouses is hard to press, and tilting the wheel is much easier and faster for me. And I use it A LOT.<br /><br />Since qt switched to xinput2, it ignores that mapping.<br />All the other buttons work fine, but not the wheel events.<br />According to this: https://bugreports.qt.io/browse/QTBUG-49345<br />it is because the wheel is treated differently.<br />Is there a way to achieve what I am trying to do?<br /><br />Thanks!<br />sjakubhttps://www.blogger.com/profile/02618969307160188601noreply@blogger.comtag:blogger.com,1999:blog-6112936277054198647.post-52469659791128439012016-04-08T00:03:47.183+10:002016-04-08T00:03:47.183+10:00Great post, Peter. I appreciate also the work to m...Great post, Peter. I appreciate also the work to make it clean upstream and the udev hwdb as consolidated point of tweaks. What you're saying probably also applies to Gnome compared to KDE - I loved all the knobs that KDE provided me, w/o thinking of the maintenance complexity there. I've been adjusting to Gnome's minimalist interface, so appreciate the reminder of the hidden values to it.<br />Anonymoushttps://www.blogger.com/profile/04820544091139170732noreply@blogger.comtag:blogger.com,1999:blog-6112936277054198647.post-79464644459551640082016-04-07T21:13:54.920+10:002016-04-07T21:13:54.920+10:00Róbert: yeah, we don't support button remappin...Róbert: yeah, we don't support button remapping outside of hardware specifics and left-handed setting. True remapping would have to be handled in the caller. You'd have to have a pretty good use-case.Peter Huttererhttps://www.blogger.com/profile/17204066043271384535noreply@blogger.comtag:blogger.com,1999:blog-6112936277054198647.post-1817549215228830072016-04-07T20:52:00.290+10:002016-04-07T20:52:00.290+10:00Ok, if 431 have top buttons enabled, I'm happy...Ok, if 431 have top buttons enabled, I'm happy. And I then obviously read the quote "Clickpad software buttons are always on the bottom edge and their size is hardcoded" to strict.<br />And I'm all for having things like that just work, instead of doing it the synaptic way (which was googling the internet for someone else that had simmilar problems, take their config and modifying it by trial and error... and after 4 hours of googling and modifying different files in /etc/ it behaved as expected... just to break the next time you upgraded the distribution). Unknownhttps://www.blogger.com/profile/08274004174610440470noreply@blogger.comtag:blogger.com,1999:blog-6112936277054198647.post-18989802337042536582016-04-07T20:32:55.692+10:002016-04-07T20:32:55.692+10:00I just want to make sure I understand it correctly...I just want to make sure I understand it correctly, you said:<br /><br />"Other features such as changing a two-finger tap to some other button event is not supported at all in libinput."<br /><br />And can I infer from this, that libinput won't support button remapping? I presume a two-finger tap is no different from any other button event? I don't think I can get my button-map accepted upstream, because it is more of a preference than a hardware quirk, so I guess I should run a patched whatever to remap buttons?Robert Khttps://www.blogger.com/profile/03063536885992421313noreply@blogger.comtag:blogger.com,1999:blog-6112936277054198647.post-14722846670785423362016-04-07T19:38:36.722+10:002016-04-07T19:38:36.722+10:00The T431 should have top software buttons enabled....The T431 should have top software buttons enabled. See<br />https://wayland.freedesktop.org/libinput/doc/latest/t440_support.html<br />If those buttons don't work, please file a bug so we can fix it.<br /><br />This is the best example for internal hardware-specific handling that previously was exposed through config options in synaptics but now just works out of the box.Peter Huttererhttps://www.blogger.com/profile/17204066043271384535noreply@blogger.comtag:blogger.com,1999:blog-6112936277054198647.post-9802878914428313752016-04-07T19:34:31.180+10:002016-04-07T19:34:31.180+10:00I'm not big on configuration settings, many ti...I'm not big on configuration settings, many times configuration is just workarounds instead of fixing the root cause. <br />However, when you write "Clickpad software buttons are always on the bottom edge and their size is hardcoded" it feels a little narrow. I have a Lenovo T431s, which requires soft buttons. However, since they have a trackpoint they also assume the buttons to be on top. They even have markings for the buttons at the top of the trackpad.<br />And I don't want to have this configurable, but for a computer like the Lenovo T431s libinput really needs to be able to have the soft buttons on top (preferably without any configuration). Unknownhttps://www.blogger.com/profile/08274004174610440470noreply@blogger.comtag:blogger.com,1999:blog-6112936277054198647.post-28376712226338830882016-04-07T13:09:28.894+10:002016-04-07T13:09:28.894+10:00Yes, it's always a balancing act. A new option...Yes, it's always a balancing act. A new option might be just 5 lines of code, but it's at least one new conditional element, adding to all the permutations that need to be covered by testing, which need to be documented, which need to be checked when the entire area gets rewritten at a later date. Actually writing code is often quite a small part of a developer's job, and the more experienced the developer, the smaller that proportion.<br /><br />And yes, sometimes options are worth the effort - your example of "tap to click' is a perfect illustration, since some people love it, some people hate it, and some people want to turn it on and off regularly depending on what they're doing, so in that case, you can't pick a single option that pleases a majority, much less everyone.<br /><br />But you have to draw a line somewhere... you can't accept every option that's proposed; at some point, figuring out how to configure all the options becomes the most complicated part of the system. I've seen more than a few apps where the Preferences window requires a search function to use, and in general, that's a bad sign.Simon Geardhttps://www.blogger.com/profile/07786893636772054343noreply@blogger.com