https://bugs.kde.org/show_bug.cgi?id=466269
--- Comment #8 from Doc <[email protected]> --- +1 for this feature request. ADDITIONAL USE CASE Conflict with Third-Party Tiling Solutions I'd like to add another perspective on why this feature is important: the hardcoded Shift modifier creates conflicts with third-party tiling scripts/extensions like KZones, Bismuth, and Polonium. Many users (myself included) prefer these third-party solutions for their additional features, configurability, or workflow preferences. However, because KWin's built-in tiling hardcodes Shift+drag, we're forced to either: 1. Configure third-party extensions to use a less intuitive modifier (Alt/Ctrl instead of Shift) 2. Accept that both systems will fight for control when using Shift+drag 3. Compile a custom KWin build to modify the hardcoded behaviour This goes against KDE's core philosophy of user choice and configurability. Users should be able to choose their preferred tiling solution without the system forcing a specific modifier key that conflicts with their choice. IMPACT: - Prevents users from fully utilising third-party tiling extensions with their preferred keybindings - Forces awkward workarounds that make window management less intuitive - Creates confusion when two tiling systems respond to the same modifier SOLUTION: A simple config option (in Settings, tile editor GUI, or kwinrc) to either: - Disable the Shift+drag behaviour entirely - Rebind it to a different modifier This would allow users to choose their tiling solution without system-level conflicts while maintaining backward compatibility (default: Shift, as it is now). -- You are receiving this mail because: You are watching all bug changes.
