The Fine Print: The following comments
are owned by whomever posted them.
( Reply )
|
Re: Menu Transparency
by anonymous on Monday 31/Dec/2001, @02:20
|
But that doesn't seem to mean it's updating what's beneath it in realtime?
|
[
Reply To This | View ]
|
Same as Liquid's. Not XRender transparency.
by Mosfet on Monday 31/Dec/2001, @02:39
|
The KDE CVS code uses the exact same code to perform translucency as Liquid. It's actually based on MegaGradient and uses QPixmap::grabWidget() to take a "snapshot" of what is behind the menu before displaying it. What it *does* do is use XRender instead of KPixmapEffect to lighten, darken, or otherwise modify the resulting image if available, but this doesn't speed up the code visibly or change the translucency at all, that is the same. In fact, it will be slower on non-accelerated XRender implementations. So I don't know what you mean by "real XRender one". Not to rain on the parade but I think it's unfair to imply that this provides a different translucency than is already available - it doesn't - otherwise I'd be using it ;-)
|
[
Reply To This | View ]
|
Re: Menu Transparency
by hash on Tuesday 01/Jan/2002, @22:05
|
no matter what you do in X, you can't get real translucent windows. it's only an illusion.
|
[
Reply To This | View ]
|
The Fine Print: The previous
comments are owned by whomever posted them.
( Reply )
|
![[KDE Dot News]](http://www.kde.org/dot/Images/kdedotnews.gif)
