Bug 501273

Summary:	Resetting tiling layouts is difficult and/or labour-intensive, because KWin remembers previous tile states until reboot, unlike other OSes.
Product:	[Plasma] kwin	Reporter:	Roke Julian Lockhart Beedell <4wy78uwh>
Component:	Quick Tiling	Assignee:	KWin default assignee <kwin-bugs-null>
Status:	RESOLVED NOT A BUG
Severity:	wishlist	CC:	john.kizer, nate
Priority:	NOR
Version First Reported In:	6.3.2
Target Milestone:	---
Platform:	Fedora RPMs
OS:	Linux
URL:	https://discuss.kde.org/t/how-to-reset-the-window-snapping-region/18509?u=rokejulianlockhart
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Roke Julian Lockhart Beedell 2025-03-09 20:01:11 UTC

SUMMARY
-------

In addition to the title, as [`discuss.kde.org/t/18509`][1] explains:

> [This Reddit post in `r/kde`][2] describes (paraphrased) a significant annoyance of mine:
> 
> > I can snap the window to the edge or the side of the screen, having side-by-side apps, or 4 apps, by placing them at the edge of the screen. Then, you can click and drag the middle point of these grids of window/app to resize the layout of all window (you can also click and drag the horizontal or vertical line). It’s a very useful feature, but I accidentally moved the middle point, and it’s not all the same size now, which is bugging me. How can I reset this middle point?
> 
> I’ve not been able to ascertain an answer online. Considering that the OP and myself know solely of a reboot being a temporarily solution, it renders the ability to resize snapped windows of more problem than worth.
> 
> This matters to me not for desire for everything to be perfect (like the OP states). Instead, because I always want my screenshots to be divisions of 2 of 16:9, lest they be rendered incorrectly in a lot of situations.
> 
> I’ve been using the "Meta" + "T" key combination to work around this, but it’s not ideal.

This behaviour isn't observed in Windows 11 Pro (OsBuildNumber: 26120).

STEPS TO REPRODUCE
------------------

-	1. Quick-Tile a window.
	2. Resize it.
	3. Untile that window.
	4. Retile it.

	OBSERVED RESULT
	---------------

	The window retains its previously resized tile state.

	EXPECTED RESULT
	---------------

	I should be able to choose to reset that state, without needing to go through the alternative tiling method.

-	1.	1. Custom-Tile a window.
		2. Resize it.
		3. Untile that window.
		4. Retile it.

		OBSERVED RESULT
		---------------

		The window retains its previously resized tile state.

		EXPECTED RESULT
		---------------

		I should be able to choose to reset that state, without needing to entirely recreate the tiling configuration (which can be really time consuming for complex layouts).

	2.	Untile that window.
	3.	Recreate the tile placements.
	4.	Retile the window.

		OBSERVED RESULT
		---------------

		The tile sizes are reset to their defaults in (at least) the custom tile layout mode.

SOFTWARE/OS VERSIONS
--------------------

-	~~~YAML
	Windows: False
	~~~

	On an affected installation, `Get-ComputerInfo` reports:

	> ~~~YAML
	> OsName: Microsoft Windows 11 Pro
	> OsOperatingSystemSKU: 48
	> OsVersion: 10.0.26120
	> OsBuildNumber: 26120
	> ~~~

-	~~~YAML
	macOS: Unknown
	~~~

	I've no VM to test this on.

-	~~~YAML
	Linux/KDE Plasma: True
	~~~

	On an affected installation, `kinfo` reports:

	> ~~~YAML
	> Operating System: Fedora Linux 41
	> KDE Plasma Version: 6.3.2
	> KDE Frameworks Version: 6.11.0
	> Qt Version: 6.8.2
	> Kernel Version: 6.13.5-200.fc41.x86_64 (64-bit)
	> Graphics Platform: Wayland
	> Processors: 12 × AMD Ryzen 5 7600X 6-Core Processor
	> Memory: 30.4 GiB of RAM
	> Graphics Processor 1: AMD Radeon RX 5700
	> Graphics Processor 2: AMD Radeon Graphics
	> ~~~

ADDITIONAL INFORMATION
----------------------

Solely the bibliography.

[1]: https://discuss.kde.org/t/how-to-reset-the-window-snapping-region/18509?u=rokejulianlockhart
[2]: https://new.reddit.com/r/kde/comments/17fawnw/how_to_reset_the_window_snapping_region/?utm_source=share&utm_medium=web2x&context=3

Comment 1 Roke Julian Lockhart Beedell 2025-03-09 20:36:46 UTC

(In reply to Roke Julian Lockhart Beedell from comment #0)  
> On an affected installation, `Get-ComputerInfo` reports:

~~~diff
1c1
- On an affected installation, `Get-ComputerInfo` reports:
---
+ On an unaffected installation, `Get-ComputerInfo` reports:
~~~

Comment 2 John Kizer 2025-03-10 18:14:06 UTC

For what it's worth - not sure if https://bugs.kde.org/show_bug.cgi?id=472369 is exactly the same thing, but it seems at least related.

Comment 3 Roke Julian Lockhart Beedell 2025-03-10 22:51:07 UTC

(In reply to John Kizer from comment #2)  
> not sure if https://bugs.kde.org/show_bug.cgi?id=472369 is exactly the same thing

Thanks, for it might well be. I'll allow the triage assignee to decide, because reading the discussions in [`invent.kde.org/plasma/kwin/-/merge_requests/5665`][2], [^1] that bug *should* be closed as RESOLVED INTENTIONAL due to the rejection of the MR, so it seems to be in somewhat of a state of flux.

[^1]: [1]

[1]: https://bugs.kde.org/show_bug.cgi?id=472369#c7
[2]: https://invent.kde.org/plasma/kwin/-/merge_requests/5665

Comment 4 Nate Graham 2025-03-11 22:23:42 UTC

Unfortunately the original bug report is practically unreadable due to the weird formatting and unnecessary information. Can you please submit human-readable bug reports in the future?

In addition, it talks about both quick tiling and custom tiling, which are different and have their own expected behaviors and bugs.

Can you please open two new bug reports: one for quick tiling, and one for custom tiling? and make sure each is written succintly without talking about other operating systems.

Thanks!

Comment 5 Roke Julian Lockhart Beedell 2025-03-14 23:06:18 UTC

(In reply to John Kizer from comment #2)

I've read the linked bug, and tentatively don't believe that it refers to what this bug does, because it discusses window resize overlap. *That*'s definitely not relevant. This bug is merely about having the tile areas' sizes reset to their defaults after all windows have been untiled.

(In reply to Nate Graham from comment #4)  

I'm not certain how to re-file this without mentioning other OSes, because describing how Quick Tiling (and its counterpart, less importantly) should act without a reference might be difficult. Do either of you have access to a Windows 11 installation? If not, I can upload a screencast from Plasma and a screencast from Windows, if that would be whatsoever useful. Alternatively, if the linked Reddit comment explains it well enough, I suppose I could steal that.

Obviously, if you think that the request is worthless, just tell me and I'll try to work this out myself, but I imagine that you've experienced this whilst attempting to capture screenshots for your blog (I presume you generally want them in 16:9)? ...Though, maybe it's too niche a use case?

Comment 6 John Kizer 2025-03-15 12:59:27 UTC

(In reply to Roke Julian Lockhart Beedell from comment #5)
> I'm not certain how to re-file this without mentioning other OSes, because
> describing how Quick Tiling (and its counterpart, less importantly) should
> act without a reference might be difficult.

If it's a feature request, describe the thing that you want to be able to do, that you currently can't do. Several different things could possibly be asked for on this topic - all of which, if implemented, would kind of get after the general comment that you referenced, but lead to different results:
ex. "I would like to be able to click on a widget, or use a keyboard shortcut, to reset the dividing line between Quick Tiled windows to the 50-50 default"
or "I would like Quick Tiling to 'snap' to pre-defined suggested proportions, including 50-50, 67-33 and 75-25"
or "I would like Quick Tiling to 'forget' the current dividing line between windows, once no windows are in a Quick Tiled state"
or "I would like to be able to toggle on/off whether Quick Tiling remembers the dividing line between windows, once no windows are in a Quick Tiled state"

etc. I personally don't think requests about the topic are worthless at all - they just need to be written clearly, specific, and actionable so they can be evaluated.

Comment 7 Roke Julian Lockhart Beedell 2025-03-23 12:42:21 UTC

(In reply to John Kizer from comment #6)  
Those are brilliant suggestions. I'll utilise them when I re-file this. Thank you.

Comment 8 Roke Julian Lockhart Beedell 2025-04-08 00:19:11 UTC

(In reply to Roke Julian Lockhart Beedell from comment #7)  
I'm beginning to think that it's actually more of a benefit than a disadvantage. Custom Tiling with 1 or 0 px borders works for this.