Bug 209163 - Translucency: inactive windows can't get more opacity
Summary: Translucency: inactive windows can't get more opacity
Status: RESOLVED DUPLICATE of bug 99198
Alias: None
Product: kwin
Classification: Plasma
Component: general (show other bugs)
Version: 4.2.4
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-10-02 01:26 UTC by Vivia Nikolaidou
Modified: 2009-10-02 03:22 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Vivia Nikolaidou 2009-10-02 01:26:46 UTC
Version:            (using KDE 4.2.4)
OS:                Linux
Installed from:    Ubuntu Packages

I enable the Translucency plugin and set inactive windows to have some a certain opacity, say X.

Now I have a certain inactive window that I don't want to be translucent. I right-click the title bar, click Opacity, and set it to 100%. It doesn't work. In fact, any opacity value lower than X works, but any opacity value higher than X leaves the window with a X opacity instead.

For example, I have set all inactive windows to have 80% opacity. I right-click a certain inactive window's title bar, click Opacity, and click 75. It works. I set the opacity to 100% at the same way but it stays at 80% instead. In order for it to become fully opaque, I have to make it active.

I then tried opening a new window using a tcl/tk interpreter and specifically tell it that I want this new window to have an alpha value of 1.0. It stays X% opaque as long as it is inactive. I try various opacity values and, just like right clicking the title bar, all values below X work and all values above X leave X as the opacity value.

I have to entirely turn off translucency for inactive windows because of this very problem, of this one inactive window that I might really need to have opaque.

Thanks for your help :)
Comment 1 Christoph Feck 2009-10-02 03:22:56 UTC
Also see duplicate bug 208421, which has some recent discussion and a possible workaround.

*** This bug has been marked as a duplicate of bug 99198 ***