[kwin] [Bug 394529] Configure Mouse buttons (e.g. setting an arbitrary button to be a "double click.")
https://bugs.kde.org/show_bug.cgi?id=394529 --- Comment #12 from Martin Flöser --- I think this is overall a wish which is just too complex. Peter's answer in the libinput request is really good. You need to change all toolkits and all compositors to support this. But changing the toolkits won't be sufficient. Even the toolkit doesn't have enough information. For a browser it is obvious where a close tab action should go to. But what to do if you have Kate in split screen with multiple tabs and maybe a Konsole window with tabs. Then you have three tab bars, where should the action go? No toolkit will be able to answer such a question. The toolkit developers will notice such issues and thus not add a general solution. And then we are back to interact with each application. As I said in my first reply: global shortcut triggering is pretty much the only possibility I can think of. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 394529] Configure Mouse buttons (e.g. setting an arbitrary button to be a "double click.")
https://bugs.kde.org/show_bug.cgi?id=394529 --- Comment #11 from sac --- OK, we need a proper solution. Apart from security, evdevremapkeys & xbindkeys don't work for productive use (GTK apps like Thunderbird remap input events, one has to click several times to trigger an action after another window had focus; totally messed up). Libinput pointed back to DE & Toolkit ( https://gitlab.freedesktop.org/libinput/libinput/issues/44 ). This affects basically every user and we expect from them to reprogram Kernels if they want to remap sth. properly :( Does noone have good connections to QT, which I guess is our last option here? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 394529] Configure Mouse buttons (e.g. setting an arbitrary button to be a "double click.")
https://bugs.kde.org/show_bug.cgi?id=394529 --- Comment #10 from Martin Flöser --- (In reply to sac from comment #9) > Understood, there's no maintainer for libinput configs ( > http://who-t.blogspot.com/2016/04/why-libinput-doesnt-have-lot-of-config. > html ) and button remapping is still a big showstopper for default wayland > on KDE. > > However, seems that there's already a deamon available > https://github.com/philipl/evdevremapkeys > > Any plans to utilize sth. like this to offer some customization options in > the settings? You can use this, but we won't add anything which utilizes this or encourages to use it. This is a huge security risk and thus is unsuited for a secure Wayland session. One of the biggest security issues of X is the possibility to generate fake input events. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 394529] Configure Mouse buttons (e.g. setting an arbitrary button to be a "double click.")
https://bugs.kde.org/show_bug.cgi?id=394529 --- Comment #9 from sac --- Understood, there's no maintainer for libinput configs ( http://who-t.blogspot.com/2016/04/why-libinput-doesnt-have-lot-of-config.html ) and button remapping is still a big showstopper for default wayland on KDE. However, seems that there's already a deamon available https://github.com/philipl/evdevremapkeys Any plans to utilize sth. like this to offer some customization options in the settings? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 394529] Configure Mouse buttons (e.g. setting an arbitrary button to be a "double click.")
https://bugs.kde.org/show_bug.cgi?id=394529 --- Comment #8 from Christoph Feck --- Changing KGlobalAccel won't help, it cannot generate mouse clicks, it only sends D-Bus messages to applications when you press the global shortcuts. Those D-Bus messages are then translated to QAction triggers. As I said, it won't help for applications that need QMouseEvent. If libinput doesn't allow plugins to generate fake input events (or remapping input events), then either the Qt toolkit would need to be expanded (very unlikely to happen, because Qt developers stay away from any type of configuration), or the applications need to handle it. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 394529] Configure Mouse buttons (e.g. setting an arbitrary button to be a "double click.")
https://bugs.kde.org/show_bug.cgi?id=394529 --- Comment #7 from sac --- So, to what should I reassign this? Or should I open a new bug to change the KGlobalAccel API, or systems settings can already make use of the API for mice as well? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 394529] Configure Mouse buttons (e.g. setting an arbitrary button to be a "double click.")
https://bugs.kde.org/show_bug.cgi?id=394529 Christoph Feck changed: What|Removed |Added Resolution|--- |WONTFIX Status|UNCONFIRMED |RESOLVED --- Comment #6 from Christoph Feck --- That does not help applications expecting a mouse click. If I understand you correctly, KDE cannot offer central customization; it has to be handled by each application individually. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 394529] Configure Mouse buttons (e.g. setting an arbitrary button to be a "double click.")
https://bugs.kde.org/show_bug.cgi?id=394529 --- Comment #5 from Martin Flöser --- (In reply to Christoph Feck from comment #4) > You mean KHotkeys? KGlobalAccel doesn't emit fake input events to > applications, as far as I know. On Wayland we will never emit fake input events. The only possible things are global shortcuts going over dbus and that's exactly what kglobalaccel does. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 394529] Configure Mouse buttons (e.g. setting an arbitrary button to be a "double click.")
https://bugs.kde.org/show_bug.cgi?id=394529 --- Comment #4 from Christoph Feck --- You mean KHotkeys? KGlobalAccel doesn't emit fake input events to applications, as far as I know. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 394529] Configure Mouse buttons (e.g. setting an arbitrary button to be a "double click.")
https://bugs.kde.org/show_bug.cgi?id=394529 --- Comment #3 from Martin Flöser --- Conceptionally this is wrong in KWin. Kglobalaccel should learn about mouse shortcuts instead. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 394529] Configure Mouse buttons (e.g. setting an arbitrary button to be a "double click.")
https://bugs.kde.org/show_bug.cgi?id=394529 Roman Gilg changed: What|Removed |Added CC||subd...@gmail.com --- Comment #2 from Roman Gilg --- There has been a GSoC project last year writing a GTK based ui for configuring gaming mice in libinput. Don't know if it got merged into GNOME or what's the current state is: https://www.hjdskes.nl/blog/gsoc-part-15/ Might be worth a look for inspiration at least. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 394529] Configure Mouse buttons (e.g. setting an arbitrary button to be a "double click.")
https://bugs.kde.org/show_bug.cgi?id=394529 Christoph Feck changed: What|Removed |Added Component|kcm_mouse |input Product|systemsettings |kwin Assignee|unassigned-b...@kde.org |kwin-bugs-n...@kde.org Severity|normal |wishlist --- Comment #1 from Christoph Feck --- Input remapping would need to be implemented in KWin for Wayland. -- You are receiving this mail because: You are watching all bug changes.
