KWin and FrameSvg

Martin Gräßlin mgraesslin at kde.org
Wed Jan 16 09:01:53 UTC 2013


Hi all,

I am currently investigating a regression in KWin: some Plasma styled elements 
always get the opaque element set.

KWin is using FrameSvgs in the following areas:
* "EffectFrames" - e.g. overlay in fullscreen effects like Cube
* PresentWindows for close window button
* DesktopGrid for add/remove desktop button
* TabBox
* DesktopChangeOSD

The usage is the following:
* EffectFrames render a "widgets/background"
* PresentWindows and DesktopGrid render a "dialogs/background"
* TabBox uses PlasmaCore.FrameSvgItem with "dialogs/background"
* DesktopChangeOSD uses PlasmaCore.Dialog, so implicitly "dialogs/background"

Everything that uses "dialogs/background" is broken and gets the opaque 
element set. Everything that uses "widgets/background" gets correctly the 
translucent set (tried changing PresentWindow and TabBox and it got correct 
elements).

This seems to be a regression with the new desktop theme. Switching to a 
different theme gives me correct translucent backgrounds, though I have not 
checked whether they are providing an opaque set.

I can rule out cache issues as the frames resize with the number of elements.

I'm a little bit at loss here. I would like to get this fixed for 4.10. Any 
advice would be very welcome. Have there been any changes? Is there a way to 
request the translucent set (KWin knows better whether Compositing is used 
than anyone else ;-)?

--
Martin Gräßlin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/plasma-devel/attachments/20130116/d8642be5/attachment.sig>


More information about the Plasma-devel mailing list