Kwin, the state of tiles?

Recently got an update and now I’m on KDE6.1, and I’m having some issues with the tiling and window positioning…

I’m using the keyboard shortcut to move a window to the left or right side of my screen.
Since my update it behaves weird. Sometimes it doesn’t separate 50/50 anymore.
Sometimes the left one takes much less space than the right one.
Not sure what’s going on.

Search made me think it is tiling, which kwin has an editor for, but I have yet to figure out how to use it since whatever I do there has no effect on any window placements.

If someone can give some update there, that would be awesome. I’m half expecting I’m missing something obvious but my search hasn’t given me any pages that could help.

Thank you all!

1 Like

The “custom tiling editor” unfortunately does not have shortcuts to tile windows to the tiles it manages - you have to drag the window and then hold shift to plug the windows into the tiles.

The behavior you describe sounds like the Quick Tiling behavior (under System Settings → Keyboard → Shortucts → KWin Look for “Quick Tile Window to X”). This used to create half-half split (or quarters) but since 6.1 you can modify the split by dragging the border of the split - so you can change the quick tile split to 40/60 or anything else.

There are two problems with this behavior:

  1. This split should reset back to 50/50 after all the quick-tiled windows are closed or untiled (“floated”), but it didn’t and that bug was fixed only very recently so you may not have that update yet (it should be in 6.1.2).
  2. If you have quick-tiled some windows and resized them on one virtual desktop, then you go to another virtual desktop and quick-tile some more windows - the second virtual desktop quick tiling splits will follow what you have set previously on the first virtual desktop. If you try to resize it then - it will also resize the first virtual desktop, because the quick-tiling layout is global for all desktops and tall activities. This bug (471893 – Resizing tiled windows (using Super+Arrow) on one virtual desktops affects all other tiled windows across all virtual desktops) is not yet fixed.
1 Like

Thank you for clarifying, with these instructions I can use the features. Indeed.

If the devs are reading this, I have to ask them:

would it not be much better for the ‘left’/‘right’ quick-tile system to be rigurous and predictable while the tiles-editor is the way for people to do more complex stuff.

I’m very much not happy that an accidental change in window size actually changes something other than the window.

I mean, I ended up opening up two konsole’s and showing the number of columns / rows, just to allow me to get back to the 50/50 setup and correct the accidental resize. (i.e. it’s an expensive thing to fix!)

If kwin must, let the resize of two windows ‘tiled’ end up resizing those windows with zero change of the quick-tiling data underneath. Which means that if I want to reset it, I just hit the shortcut again.

And let anything more complex be done with the tiling system which is opt-in.

edit: copied the above to the bug report.

There was some effort to add a setting to disable tile resizing (“lock the tiles”) here: tiling: Add option to lock tiling layout (!5665) · Merge requests · Plasma / KWin · GitLab

It is currently rejected on questions of usability/audience, but you may want to go there and comment on your use case and requirements.

I happen to agree with the ‘yet another checkbox’ not being a solution.

I didn’t manage to understand their longer term intentions, though. I just really hope they will keep things simple for the people that don’t want a full tiling experience, but like the basic quick-tiling feature KDE has had for years.

been playing with this for half an hour and i cannot find how to do this “dragging the border of the split” part.

i have noticed that the meta-T tiling only works under wayland, even tho you can create tiles in X11… but draging windows only results in the quick tile result.

and quick tile on both x11 and wayland seem to be fixed at 50% or 25% depending on where you drag it… i don’t see any way to modify that.

You use Meta + T to set up your tiling ‘Zones’, then click and hold the top bar of the window while holding shift at the same time and drag the window to the tiling zone.

Works perfectly under X11 here.

i only get that behavior under wayland

what are your details, @BulletDust ?

Operating System: Kubuntu 24.10
KDE Plasma Version: 6.1.5
KDE Frameworks Version: 6.6.0
Qt Version: 6.6.2
Kernel Version: 6.11.0-9-generic (64-bit)
Graphics Platform: X11
Processors: 28 × Intel® Core™ i7-14700K
Memory: 62.6 GiB of RAM
Graphics Processor: AMD Radeon RX 6800
Manufacturer: Micro-Star International Co., Ltd.
Product Name: MS-7D27
System Version: 1.0

This is the scenario I’m talking about:
splits

ok, i get it now thanks… so this modified split or even quartering of the screen is only valid as long as one of the windows is still tiled.

as soon as the last one goes back to floating status the modified split returns to the default 50% and 25% values for new quicktile meta+arrow operations.

the meta+t tile arrangement is still not accessible in x11 on my kubuntu 24.10 install.

Details below:

Operating System: KDE neon 6.2
KDE Plasma Version: 6.2.3
KDE Frameworks Version: 6.8.0
Qt Version: 6.8.0
Kernel Version: 6.8.0-49-generic (64-bit)
Graphics Platform: X11
Processors: 12 × Intel® Core™ i7-8700K CPU @ 3.70GHz
Memory: 31.3 GiB of RAM
Graphics Processor: NVIDIA GeForce RTX 2070 SUPER/PCIe/SSE2

Can you check the kwin logs (journalctl --user -f -u plasma-kwin_x11) and see if there are any errors about kwin/effects/tileseditor while you invoke META+T?

On my system, under wayland, I get some warnings even though it works well.

yes, these show up under X11 just now (last two entries).

file:///usr/share/kwin/effects/tileseditor/qml/main.qml:153:13: QML SpinBox: Binding loop detected for property "implicitWidth"
qt.qml.context: file:///usr/share/kwin/effects/tileseditor/qml/main.qml:21:5 Parameter "event" is not declared. Injection of parameters into signal handlers is deprecated. Use JavaScript functions with formal parameters instead.

i’ll have to relog under wayland to see if the logs show anything there, but it does work properly under wayland.

There are the same warnings I get on Wayland, where it works fine - on both Wayland and (just tested now) X11.

Do you perhaps have multiple screens?

yes, two screens… only one of which shows up in the brightness control or supports access to the settings from software.

gddccontrol gives this message when the asus monitor is selected (main monitor)

The current monitor is in the database but does not support DDC/CI.

This often occurs when you connect the VGA/DVI cable on the wrong input of monitors supporting DDC/CI only on one of its two inputs.

If your monitor has two inputs, please try to connect the cable to the other input, and then click on the refresh button near the monitor list.

but both monitors are connected via a DP cable

on the Dell monitor i get software controls in the GUI

I don’t know about brightness control (I think that’s for a different thread), but it could be a tiling editor issue with multiple screens on X11. I tried it on my system and it works for me - but it could be that you have a particular problem. I’d try opening a ticket about this and see if the developer has some idea to test.

1 Like

Should that be under kwin or plasmashell, do you think?

The tiles editor is a kwin effect and is installed as part of the kwin package.

1 Like

https://bugs.kde.org/show_bug.cgi?id=496899