Bug 208213

Summary: Combination mouse/keyboard shortcuts
Product: [Frameworks and Libraries] frameworks-kglobalaccel Reporter: Navid Zamani <navid.zamani>
Component: generalAssignee: kdelibs bugs <kdelibs-bugs>
Status: RESOLVED DUPLICATE    
Severity: wishlist CC: nate
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Gentoo Packages   
OS: Linux   
Latest Commit: Version Fixed In:

Description Navid Zamani 2009-09-22 22:32:05 UTC
Version:            (using KDE 4.3.1)
Compiler:          gcc 4.4.1 
OS:                Linux
Installed from:    Gentoo Packages

Moving over from KDE 3.5.10 with CompizFusion, I was used to some keyboard-mouse combination shortcuts, that are so efficient and great, that I would even recommend them to be standard in window managers, when toggled to "pro mode" :)

These shortcuts have a pattern like this:
<Modifier Key(s)> - <Mouse button/wheel>
<Modifier Key(s)> - <Mouse in desktop border or edge>

Some of them are possible in KDE 4. But very very limited.

For example, it is possible, to map <Win>-<Button1> to "drag window". But it is impossible to map <Win>-<Button3> to "close window" or <Win>-<Button5> to "maximize window"

These shortcuts allowed me, to completely get rid of all window title bar buttons.
There is no arguing, that hitting anywhere in the whole window is way more efficient and nice, than hitting a "stylish" tiny tiny 4px button on the border of the window. Or having huge buttons eat space for no reason.

Additionally, many multimedia keys don't work anymore. (e.g. keycode 150 [keysym 0x1008ff2f, XF86Sleep]).
(I wonder when keys up to 1024 will come, as some *others*, that also did not work before, still don't work.)
[Please, if you know the code, could you decide if I should open a separate bug for this, or if this is the same problem. Because I don't know, so I mention it here, to save adding a whole new bug if they really are the same.]
Comment 1 Nate Graham 2022-04-06 19:41:49 UTC

*** This bug has been marked as a duplicate of bug 175575 ***
Comment 2 Nate Graham 2022-04-06 19:52:06 UTC

*** This bug has been marked as a duplicate of bug 109374 ***