[kwin] [Bug 394529] Configure Mouse buttons (Global Shortcuts should accept accept mouse clicks to trigger actions/keypresses/scripts)
https://bugs.kde.org/show_bug.cgi?id=394529 Murz changed: What|Removed |Added CC||mur...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 394529] Configure Mouse buttons (Global Shortcuts should accept accept mouse clicks to trigger actions/keypresses/scripts)
https://bugs.kde.org/show_bug.cgi?id=394529 tomash...@gmail.com changed: What|Removed |Added CC||tomash...@gmail.com --- Comment #17 from tomash...@gmail.com --- For people coming here through google, the proper bug seems to be this: https://bugs.kde.org/show_bug.cgi?id=171295 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 394529] Configure Mouse buttons (Global Shortcuts should accept accept mouse clicks to trigger actions/keypresses/scripts)
https://bugs.kde.org/show_bug.cgi?id=394529 Martin Flöser changed: What|Removed |Added Resolution|--- |WONTFIX Status|UNCONFIRMED |RESOLVED --- Comment #16 from Martin Flöser --- Let's set it back to wontfix as that is the correct state from KWin perspective. Moving this feature request to kglobalaccel doesn't make sense as there is too much unrelated discussion in it. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 394529] Configure Mouse buttons (Global Shortcuts should accept accept mouse clicks to trigger actions/keypresses/scripts)
https://bugs.kde.org/show_bug.cgi?id=394529 --- Comment #15 from sac --- >Why are you reopening this ticket? How would a global shortcut help an >application that expects mouse events >This will not be fixed in KWin, according to its developers. I think you're not getting the idea here. Forget about mouse events (no mouse events in this bug report). The suggestion of the developers was to adjust global shortcuts. Currently Global Shortcuts shows the following tooltip: "Click on the button, then enter the shortcut like you would in the program. Example for CTRL+A: hold the CTRL key and press A." Instead the tooltip should say: "Click on the button, then enter the shortcut like you would in the program on your keyboard or mouse. Example for CTRL+A: hold the CTRL key and press A. Example for righ mouse button: press the right mouse button. " In addition, the option to assign a shortcut to several actions would be great. (yes, I know, just changing a tooltip is only 5% of the work, but maybe this explains it better. BTW: there are keyboards with a button for a mouse context menu. So even a mouse context menu can be triggered, if there's an action for this KEYBOARD BUTTON. Again: no mouse events here, but I'm able to customize my mouse and am even able to call batch sripts or programs [that might trigger mouse events, ugh forget that]) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 394529] Configure Mouse buttons (Global Shortcuts should accept accept mouse clicks to trigger actions/keypresses/scripts)
https://bugs.kde.org/show_bug.cgi?id=394529 --- Comment #14 from Christoph Feck --- Why are you reopening this ticket? How would a global shortcut help an application that expects mouse events to open a context menu or execute a double-click action? Global shortcuts already work, and you would have to change the application to either handle those shortcut events, or you would have to change the Qt toolkit to transform those into mouse events. This will not be fixed in KWin, according to its developers. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 394529] Configure Mouse buttons (Global Shortcuts should accept accept mouse clicks to trigger actions/keypresses/scripts)
https://bugs.kde.org/show_bug.cgi?id=394529 sac changed: What|Removed |Added Status|RESOLVED|UNCONFIRMED Summary|Configure Mouse buttons |Configure Mouse buttons |(e.g. setting an arbitrary |(Global Shortcuts should |button to be a "double |accept accept mouse clicks |click.")|to trigger ||actions/keypresses/scripts) Resolution|WONTFIX |--- --- Comment #13 from sac --- >As I said in my first reply: global shortcut triggering is pretty much the >only possibility I can think of. Got you now & renamed the bug. That solution would be perfect. @Christoph Feck GS wouldn't have to genereate mouse clicks in that case. It would just have to learn to accept those as input / trigger. In addition, the option to assign a shortcut to several actions would be great. (Maybe libinput can later cover at least the mousewheel as doubleclick case, that would help in 90% of the cases). -- You are receiving this mail because: You are watching all bug changes.
