Bug 135870 - True transparency support in yakuake
Summary: True transparency support in yakuake
Status: RESOLVED FIXED
Alias: None
Product: yakuake
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Gentoo Packages Linux
: NOR wishlist
Target Milestone: ---
Assignee: Eike Hein
URL:
Keywords:
: 272387 (view as bug list)
Depends on:
Blocks:
 
Reported: 2006-10-18 10:58 UTC by Jonathan Dehan
Modified: 2011-05-04 00:31 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Enables true transparency support (1.66 KB, patch)
2006-10-23 23:18 UTC, Jonathan Dehan 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Jonathan Dehan 2006-10-18 10:58:57 UTC 
Version:           2.75 (using KDE KDE 3.5.5)
Installed from:    Gentoo Packages
Compiler:          4.1 
OS:                Linux

Can we please have official support for true transparency in yakuake?

I got it working - all I had to do was copy the code between #ifdef COMPOSITE to the #endif from konsole/main.cpp and pasted it into  yakuake/src/main.cpp .
Comment 1 Jonathan Dehan 2006-10-23 23:18:04 UTC 
Created attachment 18238 [details]
Enables true transparency support
Comment 2 Sandra Bastian 2007-01-04 15:46:09 UTC 
*** This bug has been confirmed by popular vote. ***
Comment 3 Hans Chen 2007-02-06 15:04:21 UTC 
Jonathan Dehan: I tried your patch with Yakuake, but I get 0 % opacity as long as the schema's background is set to "Transparent". Is it possible to change the opacity?

Thanks in advance. And yes, there should be an option to enable this in Yakuake.
Comment 4 Eike Hein 2008-01-09 03:31:22 UTC 
Support for XComposite ARGB translucency is now available in the KDE 4 rewrite that has hit SVN today, replacing the pseudo-translucency of yond. Note that to get XComposite translucency in the terminal itself, you will need either KDE 4 trunk or 4.0.1. Closing.
Comment 5 Christoph Feck 2011-05-04 00:31:44 UTC 
*** Bug 272387 has been marked as a duplicate of this bug. ***