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
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
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
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,
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
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
https://bugs.kde.org/show_bug.cgi?id=394529
Christoph Feck changed:
What|Removed |Added
Resolution|--- |WONTFIX
Status|UNCONFIRMED
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
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.
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.
https://bugs.kde.org/show_bug.cgi?id=394529
Roman Gilg changed:
What|Removed |Added
CC||subd...@gmail.com
--- Comment #2 from Roman Gilg
https://bugs.kde.org/show_bug.cgi?id=394529
Christoph Feck changed:
What|Removed |Added
Component|kcm_mouse |input
Product|systemsettings
12 matches
Mail list logo
