Version: unspecified (using KDE 4.4.5) OS: Linux I used the right mouse button on title bar to set the opacity from the context menu. This works. I alt-tab to another window and the opacity is reset to it's original state. When i return to the window the opacity remains at it's original state. Also i set the title bar wheel event to change opacity. Again this works, but after switching windows, the opacity is reset. Not sure if Desktop Effects are interfering. Translucency is not enabled. Dim Inactive was enabled, but i just disabled it and re-tested. Same result. This happens for any window KDE or non-KDE, e.g. Firefox/Iceweasel, Blender, Gimp. Reproducible: Always Steps to Reproduce: Start with a Window-Specific rule for all windows, all types (except Desktop), with Active opacity 80% and Inactive opacity 80%. Right click on title bar, select opacity, set to 100%. alt-tab Actual Results: Window opacity set to ~ 80%. Expected Results: Window remains at 100%. Other enabled desktop effects include: Fade, Login, Logout, Minimize Animation, Shadow, Slide, Sliding popups, Taskbar, Thumbnails, Dialog Parent, Box Switch[1], Cover Switch, Desktop Cube, Desktop Grid, Flip Switch, Present Windows. [1] Though i just disabled that and re-tested. Also this is my effect for window switching.
the rule says "force", so this behaviour is "correct" you want a "remember" policy, which would have to be implemented. (therefore "wishlist" severity)
While i agree that's a force rule, i would expect a local setting at the window would override any general rule. My 2 cents here, it doesn't seem right to set this 80% opacity rule to "remember". What does that mean? (Heck what does force temporary mean?) I think either stick with "force" or use the word "default". Also i suggest at the window level (title bar) add an option "system-default". Or thinking of it differently, setting opacity 100% at the window can set a new rule which is more specific than "all windows". When i set a window opacity to 100%, i do not see a new rule generated. I just assume that rules are applied in some order. The best i can find off the cuff is kwin / rules.cpp / match() and findWindowRules().
no, force means "force" - actually it should not even allow you to alter the opacity (like if you force a desktop you cannot leave it at all) and yes: the rules (a very old item in KDE) are not a good thing for end users because of obsscure complexity. that however doesn't fix that you want a remember rule, trust me ;-) ("remember to not re-apply the rule once the value has been overridden")
I confirm this bug still persits on 4.7.0. Oddly enough, "Force" seems to do what I want it to (I can still change the opacity by hand), while using "Force temporarily" doesn't make the opacity settings persitent.