Bug 467516 - Collision between Mouse Mark and Custom Tiling keyboard shortcuts
Summary: Collision between Mouse Mark and Custom Tiling keyboard shortcuts
Status: RESOLVED DUPLICATE of bug 337043
Alias: None
Product: kwin
Classification: Plasma
Component: effects-various (show other bugs)
Version: 5.27.2
Platform: Gentoo Packages Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-03-18 09:20 UTC by Naxdy
Modified: 2023-06-23 01:32 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Naxdy 2023-03-18 09:20:39 UTC
SUMMARY
Currently, the shortcut for mouse marking is Meta+Shift, and cannot be changed. The hotkey to custom tile a window while dragging is Shift, which again cannot be changed.

This results in a collision of hotkeys, when a user is using the Meta key to drag a window by clicking anywhere, and is attempting to custom tile it. If the Mouse Mark effect is also activated at the same time, this will result in red streaks all over the screen whenever the user is using Meta+Shift to custom tile a window.

SOLUTION
1. Change the Mouse Mark shortcut from Meta+Shift to something else (I propose Meta+Control).
2. Allow the user to customize both the custom tiling hotkey, as well as the Mouse Mark shortcut.


SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Gentoo
(available in About System)
KDE Plasma Version: 5.27.2
KDE Frameworks Version: 5.103.0
Qt Version: 5.15.8

ADDITIONAL INFORMATION
-
Comment 1 David Edmundson 2023-04-03 11:17:07 UTC
We don't want to throw in some settings, we need to fix it for users out-of-the-box.
Comment 2 Naxdy 2023-04-03 12:12:13 UTC
Then I see solution 1 as the only viable option.

Though I'm not sure if Meta+Control would incur any other collisions.
Comment 3 Andrew Shark 2023-06-23 01:32:51 UTC
There is a duplicate Bug 466157, which itself is a duplicate of Bug 337043.

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