Bug 485620

Summary: Adjust the default shortcut for Mouse Mark
Product: [Plasma] kwin Reporter: Antti Savolainen <antti.savo>
Component: effects-variousAssignee: KWin default assignee <kwin-bugs-null>
Status: RESOLVED DUPLICATE    
Severity: wishlist CC: fanzhuyifan
Priority: NOR    
Version: 6.0.3   
Target Milestone: ---   
Platform: Arch Linux   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Antti Savolainen 2024-04-16 04:50:29 UTC
SUMMARY
Demonstrative video: https://youtu.be/Zv2HtjkSskE
I feel that the default shortcut for Mouse Mark overlaps with the default hotkey for rectangular screenshot too much. Currently Mouse Mark is done with Ctrl+Shift+Mouse Move while Rectangular screenshot is Ctrl+Shift+PrintScreen. This can lead to situations where a small movement of the mouse can leave a smidge on the screen right before trying to take a shot. In the demonstrative video I demonstrate it with bug 485619 to exaggarate the effect, but even a small smidge could be annoying. 
I propose that the binding should be moved to Ctrl+Shift+Mouse Click+Drag

SOFTWARE/OS VERSIONS
Linux: Arch Linux
KDE Plasma Version: 6.0.3
KDE Frameworks Version: 6.0.0
Qt Version: 6.7.0
Comment 1 fanzhuyifan 2024-04-21 16:44:52 UTC
Does this annoying behavior still occur in 6.0.4, where bug 485619 has been fixed?
Comment 2 Antti Savolainen 2024-04-22 00:21:03 UTC
I merely used the bug to exaggarate the effect. In practice the issue would be caused by first holding down Super+Shift and then moving my other hand from the mouse to the print screen button. It would look like this in practice: https://youtu.be/J9ur7UNyxcM

Oh btw, I said the wrong bindings in the original report. I said Ctrl+Shift when I should have said Super+Shift
Comment 3 fanzhuyifan 2024-04-22 02:05:13 UTC
Btw the binding is configurable, so you could change it so ctrl+shift if you find it annoying.
Comment 4 Antti Savolainen 2024-04-22 02:16:04 UTC
Yeah, I get that. I just wish to improve the experience for the people that come after me.
Comment 5 Antti Savolainen 2024-09-14 10:35:33 UTC
*** This bug has been marked as a duplicate of bug 491706 ***