SUMMARY When using one monitor, repeating the same quick tile shortcut key does not untile (restore) the window to its original size and location. STEPS TO REPRODUCE 1. Have one monitor 2. Focus any window, e.g. a Dolphin window 3. Press the shortcut key to quick tile the window to the left or ride side of the screen (e.g. super/meta+left) 3. Press the shortcut key again OBSERVED RESULT The window stays tiled. EXPECTED RESULT The window should untile/restore to its previous position. I have to maximize and restore the window to restore it. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 6.3.1 KDE Frameworks Version: 6.11.0 Qt Version: 6.8.2 Kernel Version: 6.13.3-arch1-1 (64-bit) Graphics Platform: Wayland ADDITIONAL INFORMATION This used to work until I updated to 6.3.1 yesterday. Unfortunately, I don't know what my previously installed version was. I'm relatively certain that this bug fix has caused the issue: https://bugs.kde.org/show_bug.cgi?id=493607 Here, it's quite suspicious to me that all the `N` cases are gone (but I don't understand the code enough to draw any conclusions from it): https://invent.kde.org/plasma/kwin/-/commit/596ce0b3a08b2fd304b809d923ff21267e25dc65#b511e90f6b6d5af94f4af5fcac5d7e2497a3c15a_653_653
This was an intentional change that was arrived at after a very long discussion and broad consensus; the old behavior was very confusing in many circumstances especially with multiple monitors - you can find more information about this on invent. I remember there being talk about introducing a keyboard shortcut for untiling though, if there was demand for it. As maximizing and unmaximizing is not quite obvious and there are people that would like to untile using the keyboard, I think it makes sense to repurpose this one for that instead of closing as intentional. Retitling accordingly.
This is intentional at this point in time; the reault of a UX overhaul of how quick tiling works to make it more "spatial". If you find yourself needing to regularly un-tile windows, you can do it using the method you already found. I can see the utility to adding an action to make this possible directly, though.
I'm sorry, but this reminds me a little of the XKCD 1172 Workflow comic. In particular: If you find yourself needing to regularly un-tile windows, you can do it using the method you already found. Previously, I was able to do it with one keystroke. A method that, as far as I remember, I have been using for years in Windows too (though I haven't used it in a few years anymore). I can very much understand that it was confusing when using multiple monitors, and I respect that the change was made for users with multiple monitors. But it did break the workflow or expectations of those who do not have multiple monitors. Doing a maximize and then a restore I do not find a satisfying work-around, especially since I've been using the same keystroke to tile and un-tile for years before. On top of that, maximizing and un-maximizing a window looks extremely janky on my ultra-wide... I am grateful that this bug has been repurposed into a feature request to provide a shortcut key to restore/un-tile windows. I hope it can be delivered soon.
Excuse my tone; my frustration of my workflow being impeded got the better of me. I really respect your hard work to deliver this great free and open-source project a lot. I will be more careful and friendlier in my wording from now on.
It's all good :)
Hello, I heavily relied on this behavior before it was removed and am unhappy it is being treated as a feature request rather than a regression. Does anyone on this issue have any advice for bringing back the previous behavior, via kwin scripts or otherwise? I understand removing this feature may be more intuitive for those who commonly use multiple monitors. But, my usage revolves around my small laptop screen, and being able to tile and un-tile with the same shortcut is invaluable. I was hoping that this was a bug, and to be honest I'm fairly annoyed/surprised it was intentional -- seems the time for feature discussion is long past though.
I'd also appreciate a workaround.