Bug 473779

Summary: Window transparency labels are misleading and "restore button not working"?
Product: [Applications] systemsettings Reporter: Zyon <zyonistz>
Component: kcm_kwinrulesAssignee: KWin default assignee <kwin-bugs-null>
Status: RESOLVED WORKSFORME    
Severity: normal CC: isma.af, nate, plasma-bugs
Priority: NOR    
Version: 5.27.7   
Target Milestone: ---   
Platform: Arch Linux   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Zyon 2023-08-26 16:38:49 UTC 
(English is not my first language, sorry if the things here are writter weirdly or if i missunderstood something)

When changing the window opacity the DEFAULT % is 0% shoud mean no opacity as the title and bar sugests that you are at the start point, and the more you add on the percentage, is the more transparent your window will become, but the opposit happens, and without any "easy" restore button, or reset countdown it is easy to missunderstand what it is saying and by misstake make all your windows invisible.


STEPS TO REPRODUCE
(https://youtu.be/LgZ8UJLtAc4?si=8BItXrXBDQC2b_UG&t=58)
1.  Press Alt+f3
2.  Click on the "More actions" option
3.  Click on the "Configure special windows settings"
4.  Click on the "Add property" 
5.  Scroll down until you find "Active opacity" and/or "inactive opacity" and select them

SOFTWARE/OS VERSIONS:

Operating System: Arch Linux 
KDE Plasma Version: 5.27.7
KDE Frameworks Version: 5.109.0
Qt Version: 5.15.10
Kernel Version: 6.4.12-arch1-1 (64-bit)
Graphics Platform: Wayland
Graphics Processor: Mesa Intel® UHD Graphics 630


ADDITIONAL INFORMATION

The 0% transparency should mean NO transparency, not 100% transparency 
(https://youtu.be/LgZ8UJLtAc4?si=QoMsBxsAm-61W1aU&t=74) 'Nicco' just added this configuration, and it is at 0% meaning it should be the "NO transparency" percentage

It should ask with a timer if you want to keep this change, the same timer the resolution setting has as an way to not break the system

The reset button should instantly reset to default not open another tab to import/export the config 

The things you change should stay there not get back to the "add priority" tab so you know what you changed before

(also, the timer at the bottom seems not to be working? it feels like it's doing nothing and putting the mouse above it says nothing about it)
Comment 1 Ismael Asensio 2023-08-28 20:50:06 UTC 
Hi! Thanks for your bug report but I don't understand exactly what the bug is.

The label reads opacity and  the default was already fixed to be 100%. Meaning opacity 100% = no transparency and opacity 0% no visibility. The mentioned video was recorded before that default was changed.

Is the default still 0% by default ifor you instead of 100% when adding an opacity property?

We discussed before about limiting the value to avoid users making a mistake. But window rules is considered an advanced feature and we shouldn't limit what users can do with it, because it is precisely meant for niche cases to override the regular functionally of some windows.

The module already warns against applying any rule to all windows without filtering by class or window type.
Comment 2 Bug Janitor Service 2023-09-12 03:45:18 UTC 
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 3 Bug Janitor Service 2023-09-27 03:46:15 UTC 
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!