trinity-devel@lists.pearsoncomputing.net

Message: previous - next
Month: February 2012

Re: [trinity-devel] twin modifications

From: "Timothy Pearson" <kb9vqf@...>
Date: Mon, 13 Feb 2012 15:00:59 -0600
> On Tuesday 14 February 2012 00:52:19 Timothy Pearson wrote:
>
>> > http://storage3.static.itmages.ru/i/12/0214/h_1329165438_7516085_4b941fd1da.png
>> >
>> > And this is how the shadows look like:
>> >
>> > http://storage9.static.itmages.ru/i/12/0214/h_1329165743_2170554_d5f80f5a0b.png
>>
>> Yep, those are the kompmgr composited shadows, which are present in TDE
>> and are the ones I want to keep.  The other shadows in question are not
>> composited and are very glitchy as a result.
>
> No. These shadows are not those present in TDE. TDE currently uses the
> shadows introduced
> by the cited above Chakra patch. The shadows on this screenshot are the
> original kwin shadows.

While they are original, they are in fact handled by kompmgr. :-)  There
are also non-composited shadows that originally came with KDE 3.5.10 as
well, and those are glitchy.

The checkbox in your screenshot is not very accurate.  In TDE it has been
changed to read ""Enable the Trinity window composition manager" instead
of "Use Translucency/Shadows", and if you dig around in the KDE 3.5.10
code a bit you will see what I mean.

kompmgr's shadows (which incidentally are configured using the exact same
kcontrol module with the same general options) work almost 100% on the TDE
system that I am writing this from...

Does this make things a bit clearer?

Tim