Summary: | add remember policy to active/inactive opacity rules | ||
---|---|---|---|
Product: | [Plasma] kwin | Reporter: | Brian DeRocher <brian> |
Component: | rules | Assignee: | KWin default assignee <kwin-bugs-null> |
Status: | REPORTED --- | ||
Severity: | wishlist | CC: | isma.af, matija, nate |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Debian unstable | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
Brian DeRocher
2010-12-24 15:45:04 UTC
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. |