Bug 471922

Summary:	Make difference between "properties you already set" and "properties you can set" more clear
Product:	[Applications] systemsettings	Reporter:	Henning <boredsquirrel>
Component:	kcm_kwinrules	Assignee:	KWin default assignee <kwin-bugs-null>
Status:	ASSIGNED ---
Severity:	wishlist	CC:	isma.af, nate, plasma-bugs-null
Priority:	NOR	Keywords:	usability
Version First Reported In:	5.27.4
Target Milestone:	---
Platform:	unspecified
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Henning 2023-07-03 22:54:06 UTC

Differenciate more between "properties already existant" and "values you want".

At the moment it makes no real sense, you enter the values that should detect the window, and the values you want in the same. How does it even decide if I want a fullscreen window always on top, or an always on top window always in fullscreen? There is a difference.

Comment 1 Ismael Asensio 2023-09-28 17:17:51 UTC

*** Bug 474978 has been marked as a duplicate of this bug. ***

Comment 2 Ismael Asensio 2023-09-28 17:25:23 UTC

Hi there!

As you mentioned in the other report, there is only one set of properties to match (those under "Window matching"), and all of the other properties you override (set/force/etc) on the window that matches those.

It is challenging to show a distinction between those (beside being in a different section), while keeping the code and the UI not extremely complex. But I think it is a legitimate question and with some latest visual components, I have some idea on how to improve a bit on that.

Comment 3 Henning 2023-10-12 21:49:43 UTC

Thanks! Yes it was also a question if it actually works like this, and I suppose it does. having that distinction would be great and really needed, even though it currently somehow works, I guess

Comment 4 Bug Janitor Service 2024-07-22 14:05:33 UTC

A possibly relevant merge request was started @ https://invent.kde.org/plasma/kwin/-/merge_requests/6154