On Monday, July 18, 2011 21:36:54 Martin Gräßlin wrote:
> I am not aware of any XServer not supporting the named extensions. To be
> sure I will also post this mail to the packagers mailinglist if nobody
> contradicts me here on KWin and Plasma till let's say end of this week.
>
> Opinions?
build
Hi all,
KWin currently has the following optional build dependencies which I would like
to turn into hard
build dependencies:
* OpenGL or OpenGL ES
* XComposite
* XDamage
* XRender
* XFixes
I consider KWin as a Compositor and Window Manager, so I think it is at the
time to require KWin
to be
On Monday 18 July 2011 15:12:29 Fredrik Höglund wrote:
> On Monday 18 July 2011, Aaron J. Seigo wrote:
> > On Saturday, July 16, 2011 15:36:19 Martin Gräßlin wrote:
> > > The bug is much simpler - Plasma just simply fails to recognize that a
> > > compositing manager is active. I can see this each
---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/101968/#review4820
---
This review has been submitted with commit
5ee3119417b0366ba867
On Monday 18 July 2011, Aaron J. Seigo wrote:
> On Saturday, July 16, 2011 15:36:19 Martin Gräßlin wrote:
> > The bug is much simpler - Plasma just simply fails to recognize that a
> > compositing manager is active. I can see this each time I restart kwin
> > (which is considerable often). In order
> On Feb. 26, 2011, 1:31 p.m., Marco Martin wrote:
> > hmm i'm not sure about it, i don't see an huge use case of showing icons
> > that are meant to be passive (so not telling anything useful at the moment)
> >
> > however the patch is well done (i appreciate disabling the combo boxes when
>
---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/101968/#review4810
---
Ship it!
a brown paper bag moment. doh! thanks for catching thi
On 07/18/2011 11:53 AM, Aaron J. Seigo wrote:
> * a race condition as Alex outlined. if kwin is indeed responding to each
> xrandr even with a change in the CM, that seems like a perfect candidate for
> event compression if at all possible: don't tell the world outside that things
> have changed un
On Saturday, July 16, 2011 15:36:19 Martin Gräßlin wrote:
> The bug is much simpler - Plasma just simply fails to recognize that a
> compositing manager is active. I can see this each time I restart kwin
> (which is considerable often). In order to get translucent panels back, I
> have to kquitapp
On Sunday, July 17, 2011 18:00:28 Marco Martin wrote:
> > we can still share _one_ instance of the structure for multiple Package
> > classes, something we haven't been able to do since the introduction of
> > configChanged a couple years ago, actually, and Package will still be
> > passed by refer
I have installed Ruby-Clock Analog. But I don't like it, because it simply
does not show any time whatsoever. Rather useless, in my opinion.
But I cannot uninstallit either. I can click on the "X" and then it is gone
for the time being, but next time it is present again.
How can I get rid of it
On 07/16/2011 04:01 PM, Alex Fiestas wrote:
>> If anyone knows where to look at in Plasma code, I would try to fix it
>> as it deeply annoys me.
> Same here.
The magic accours in libplasma theme.cpp.
___
Plasma-devel mailing list
Plasma-devel@kde.org
htt
On 07/16/2011 03:36 PM, Martin Gräßlin wrote:
> On Saturday 16 July 2011 15:24:56 Alex Fiestas wrote:
>> Hi there
>>
>> One of the issues I have when I setup my XRandR config is that plasma
>> fails to set the composite theme (the good looking with ARGB one).
>>
>> After thinking about it a little
Hi there
One of the issues I have when I setup my XRandR config is that plasma
fails to set the composite theme (the good looking with ARGB one).
After thinking about it a little bit, and knowing how KWin and Plasma
are handling XRandR events I think I know where the bug is.
When adding a new
14 matches
Mail list logo
