Summary: | JJ: Disable Translucency effect during fullscreen effect | ||
---|---|---|---|
Product: | [Plasma] kwin | Reporter: | Jonathan Thomas <echidnaman> |
Component: | compositing | Assignee: | KWin default assignee <kwin-bugs-null> |
Status: | RESOLVED INTENTIONAL | ||
Severity: | wishlist | Keywords: | junior-jobs |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Unspecified | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Jonathan Thomas
2008-11-06 14:54:49 UTC
Personally I think the best solution would be that transparency is disabled at all during coverswitch. Transparency and coverswitch together do not make any sense in my opinion. Therefor we need a way to disable a different effect dynamically. Which is not yet available and due to upcoming feature freeze won't be there for 4.2. I think there's already an open bug for it and I would say this bug's a duplicate of it. Can't you like... just not multiply by data.opacity? Well I could reset the value to 1.0, but that would not help if another effect processed after coverswitch changes the values again. Yes that is true, completely forgot you've changed how the effect works. ^_^; Easy solution: translucency effect should not alter windows while a fullscreen effect is active. Fullscreen effects take care of the complete window alteration. After thinking over it again I don't think there is anything wrong. If a user sets the windows to be transparent, then they are transparent. Not all effects make sense working together and it is totally fine to have an effect which makes another effect less usable. Given the number of effects and the complexity derived by that it is just impossible to even try to achieve that everything works perfectly well together. That said and given the time since the feature request has been opened it is probably the most honest thing to say that we won't fix this request. |