Version: unspecified (using KDE 4.5.0) OS: Linux Using the new tiling mode in KWin with multiple desktops, if on one desktop there is only one window and you drag it by it's titlebar it gets floated, which is a correct behavior I assume. However, upon switching to another desktop I see that the previously maximised window I had there changed it's size and became a floating window too. Reproducible: Always Steps to Reproduce: - Set up multiple virtual desktops - Activate window tiling - Open one window on each desktop and maximize them - Drag one of the windows by their titlebar Actual Results: Both windows get unmaximised and enter the floating state Expected Results: Only the window that is being dragged should get unmaximised
Similiar unexpected result: 1, Open two windows on two virtual desktop in tiling mode. 2, Drag the first window to the edge to unmaximize it. 3, Drag the second window to no where (just drag a little without changing anything. and it is the same if I really drag it to the edge to unmaximize it.) Expected Result: The first window should still unmaximized. Actual Result: All the windows on other virtual desktops are maximized.
Oh, btw, I am using Arch Linux with testing enabled. My kdebase-workspace version is 4.7.4-2
"kcmshell4 kwinoptions", "moving" tab, check "display borders on maximized windows" "kcmshell4 kwinscreenedges", uncheck "maximize windows by dragging..." also see bug #246153 @martin & myself: we must spellbind the quick maximization setting if we spellbind the window borders (cause they are known to cross each other)
(In reply to comment #3) > "kcmshell4 kwinoptions", "moving" tab, check "display borders on maximized > windows" > "kcmshell4 kwinscreenedges", uncheck "maximize windows by dragging..." > Afaik, the first one helps nothing and the second one certainly hide the bug because I cannot unmaximazed (untile) the window at all in tiling mode. > also see bug #246153 > > @martin & myself: we must spellbind the quick maximization setting if we > spellbind the window borders (cause they are known to cross each other)
As of git commit 34027455aaa2ee738c45987ca2d8cb7d65491bf0 window tiling support has been removed from KWin. This change will go into version 4.10, the upcoming release 4.9 still provides window tiling support. The discussion has been taken on the developer mailing list [1]. A short summary of the reasons here: * it is unmaintained * it is a mode not used by any of the core KWin team * original developer said at Akademy 2012 that he is not interested in picking up the work again * tiling has quite some bugs, e.g. multi screen not supported * is conflicting with other concepts in KWin, e.g. activities A result of this change is that we will not implement any new features or fix bugs related to window tiling. There is ongoing work to provide window tiling as an external KWin script. We encourage everyone to participate in this effort and to make it really rock and have it available once 4.10 is going to be released. The current state can be found in the git repository [2] in the directory kwin/scripts/tiling. [1] http://lists.kde.org/?l=kwin&m=133149673110558&w=2 [2] https://github.com/mgottschlag/kwin-tiling/