[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kwin
Subject:    Re: patch for #167138 (opacity rules ignored)
From:       Martin =?iso-8859-15?q?Gr=E4=DFlin?= <kde () martin-graesslin ! com>
Date:       2009-07-24 5:36:43
Message-ID: 200907240736.50377.kde () martin-graesslin ! com
[Download RAW message or body]

[Attachment #2 (multipart/signed)]


Am Freitag 24 Juli 2009 01:09:58 schrieb Thomas L=FCbking:
> Am Thursday 23 July 2009 schrieb Martin Gr=E4=DFlin:
> > Looks good to me (but not yet tested), just one question: how does it
> > behave when setting the opacity in the alt+f3 menu?
>
> applied until the next (de)activation
> there's so far no "remember" config - you can just force [temp] - and i
> mostly wnated to get rid of the broken config item in one or the other wa=
y.
good point
>
> > Personally I would prefer to have a kind of window specific rules for t=
he
> > effects and to move the opacity rule to the translucency effect.
>
> the opacity is a _NET_WM property on the window so
> a)  in particular in this case we'll probably have to care to keep visual
> and attrib in sync?!? as...
> b) ...the attribute is effectively set - w/ or w/o composition support -
> and can be read by e.g. the application.
that doesn't sound nice :-/ Hmm probably there is no other way.
>
> > has the time we have to live with that solution which is much better th=
an
>
> the broken state it was before :-D
>
> i'll set the rule for some windows and test for another to days, then
> commit if nobody yelled "STOP!" meanwhile (as you might have noticed in t=
he
> patch, i also needed to modify the EffectsHandlerImpl to prevent an
> incredibly annoying segfault ;-)
That's the reason for that return - I wondered why you added it :-D

Sounds like a good plan :-)

["signature.asc" (application/pgp-signature)]

_______________________________________________
kwin mailing list
kwin@kde.org
https://mail.kde.org/mailman/listinfo/kwin


[prev in list] [next in list] [prev in thread] [next in thread]