[prev in list] [next in list] [prev in thread] [next in thread]
List: kwin
Subject: Re: Review Request: Delay added signal and other signal bindings for synced windows until the window
From: Martin_Gräßlin <kde () martin-graesslin ! com>
Date: 2012-01-24 19:04:45
Message-ID: 20120124190445.6209.77952 () vidsolbach ! de
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
> On Jan. 21, 2012, 5:19 p.m., Philipp Knechtges wrote:
> > Although I agree with you that the effects shouldn't be bothered with a=
window that isn't shown once,
> > I would prefer to make the emitted signals consistent. Your current app=
roach has the shortcoming that
> > it might not emit the windowAdded signal, but on the other hand it woul=
d always emit windowClosed
> > and windowDeleted.
> =
> Thomas L=C3=BCbking wrote:
> i hope not. those are connected in setupClientConnections()now being =
invoked by slotClientShown() which is not called unless the window is or go=
t readyForPainting()
> =
> ie. the connection is cut off on the effectshandler
> =
> Philipp Knechtges wrote:
> Ok, must have overseen that :)
> You're right for windowClosed but the slotDeletedRemoved is connected=
in the EffectsHandlerImpl ctor to a workspace event which itself gets
> called from the Deleted destructor.
> =
> Thomas L=C3=BCbking wrote:
> shouldn't harm and is actually correct. deleted is only relevant to c=
lean up data, not to trigger stuff. therefore it's likely been bound regard=
less for better robustness.
> =
> we can probably hide it from assumingly unbound windows, but that mig=
ht cause trouble in case effect internal data ever invoked the stacking ord=
er (and thus may contain references to unconnected effectWindows which woul=
d turn into dangles (can one noun dangle? :)
agreed that keeping the deleted signal will not harm and I do not like to p=
lay with it :-) So keeping it is the best thing
My suggestion in general for this request is to ship it to master, watch th=
e behavior and if everything is fine push it to 4.8 branch before 4.8.1 tag=
ging.
This includes a ship it which is not possible to be set when writing a comm=
ent.
- Martin
-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/103742/#review9984
-----------------------------------------------------------
On Jan. 20, 2012, 2:21 a.m., Thomas L=C3=BCbking wrote:
> =
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> http://git.reviewboard.kde.org/r/103742/
> -----------------------------------------------------------
> =
> (Updated Jan. 20, 2012, 2:21 a.m.)
> =
> =
> Review request for kwin, Martin Gr=C3=A4=C3=9Flin and Philipp Knechtges.
> =
> =
> Description
> -------
> =
> see summary. Makes animations smoother and would have prevented RR http:/=
/git.reviewboard.kde.org/r/103733 ;-)
> =
> I'll keep it in my personal 4.8 branch and therefore won't care about whe=
ther it's applied to 4.8.n or 4.9 :-P
> =
> =
> Diffs
> -----
> =
> kwin/client.cpp 520ed85 =
> kwin/composite.cpp 55a7144 =
> kwin/effects.h f4ad2fb =
> kwin/effects.cpp 6c252c9 =
> kwin/events.cpp 26e0139 =
> kwin/toplevel.h 693e6f3 =
> kwin/toplevel.cpp ffe7f0c =
> =
> Diff: http://git.reviewboard.kde.org/r/103742/diff/diff
> =
> =
> Testing
> -------
> =
> generic animations still work - better ;-)
> =
> =
> Thanks,
> =
> Thomas L=C3=BCbking
> =
>
[Attachment #5 (text/html)]
<html>
<body>
<div style="font-family: Verdana, Arial, Helvetica, Sans-Serif;">
<table bgcolor="#f9f3c9" width="100%" cellpadding="8" style="border: 1px #c9c399 \
solid;"> <tr>
<td>
This is an automatically generated e-mail. To reply, visit:
<a href="http://git.reviewboard.kde.org/r/103742/">http://git.reviewboard.kde.org/r/103742/</a>
</td>
</tr>
</table>
<br />
<blockquote style="margin-left: 1em; border-left: 2px solid #d0d0d0; padding-left: \
10px;"> <p style="margin-top: 0;">On January 21st, 2012, 5:19 p.m., <b>Philipp \
Knechtges</b> wrote:</p> <blockquote style="margin-left: 1em; border-left: 2px solid \
#d0d0d0; padding-left: 10px;"> <pre style="white-space: pre-wrap; white-space: \
-moz-pre-wrap; white-space: -pre-wrap; white-space: -o-pre-wrap; word-wrap: \
break-word;">Although I agree with you that the effects shouldn't be bothered \
with a window that isn't shown once, I would prefer to make the emitted signals \
consistent. Your current approach has the shortcoming that it might not emit the \
windowAdded signal, but on the other hand it would always emit windowClosed and \
windowDeleted.</pre> </blockquote>
<p>On January 21st, 2012, 5:43 p.m., <b>Thomas Lübking</b> wrote:</p>
<blockquote style="margin-left: 1em; border-left: 2px solid #d0d0d0; padding-left: \
10px;"> <pre style="white-space: pre-wrap; white-space: -moz-pre-wrap; white-space: \
-pre-wrap; white-space: -o-pre-wrap; word-wrap: break-word;">i hope not. those are \
connected in setupClientConnections()now being invoked by slotClientShown() which is \
not called unless the window is or got readyForPainting()
ie. the connection is cut off on the effectshandler</pre>
</blockquote>
<p>On January 21st, 2012, 5:51 p.m., <b>Philipp Knechtges</b> wrote:</p>
<blockquote style="margin-left: 1em; border-left: 2px solid #d0d0d0; padding-left: \
10px;"> <pre style="white-space: pre-wrap; white-space: -moz-pre-wrap; white-space: \
-pre-wrap; white-space: -o-pre-wrap; word-wrap: break-word;">Ok, must have overseen \
that :) You're right for windowClosed but the slotDeletedRemoved is connected in \
the EffectsHandlerImpl ctor to a workspace event which itself gets called from the \
Deleted destructor.</pre> </blockquote>
<p>On January 21st, 2012, 6:16 p.m., <b>Thomas Lübking</b> wrote:</p>
<blockquote style="margin-left: 1em; border-left: 2px solid #d0d0d0; padding-left: \
10px;"> <pre style="white-space: pre-wrap; white-space: -moz-pre-wrap; white-space: \
-pre-wrap; white-space: -o-pre-wrap; word-wrap: break-word;">shouldn't harm and \
is actually correct. deleted is only relevant to clean up data, not to trigger stuff. \
therefore it's likely been bound regardless for better robustness.
we can probably hide it from assumingly unbound windows, but that might cause trouble \
in case effect internal data ever invoked the stacking order (and thus may contain \
references to unconnected effectWindows which would turn into dangles (can one noun \
dangle? :)</pre> </blockquote>
</blockquote>
<pre style="white-space: pre-wrap; white-space: -moz-pre-wrap; white-space: \
-pre-wrap; white-space: -o-pre-wrap; word-wrap: break-word;">agreed that keeping the \
deleted signal will not harm and I do not like to play with it :-) So keeping it is \
the best thing
My suggestion in general for this request is to ship it to master, watch the behavior \
and if everything is fine push it to 4.8 branch before 4.8.1 tagging.
This includes a ship it which is not possible to be set when writing a comment.</pre>
<br />
<p>- Martin</p>
<br />
<p>On January 20th, 2012, 2:21 a.m., Thomas Lübking wrote:</p>
<table bgcolor="#fefadf" width="100%" cellspacing="0" cellpadding="8" \
style="background-image: \
url('http://git.reviewboard.kde.org/media/rb/images/review_request_box_top_bg.png'); \
background-position: left top; background-repeat: repeat-x; border: 1px black \
solid;"> <tr>
<td>
<div>Review request for kwin, Martin Gräßlin and Philipp Knechtges.</div>
<div>By Thomas Lübking.</div>
<p style="color: grey;"><i>Updated Jan. 20, 2012, 2:21 a.m.</i></p>
<h1 style="color: #575012; font-size: 10pt; margin-top: 1.5em;">Description </h1>
<table width="100%" bgcolor="#ffffff" cellspacing="0" cellpadding="10" \
style="border: 1px solid #b8b5a0"> <tr>
<td>
<pre style="margin: 0; padding: 0; white-space: pre-wrap; white-space: \
-moz-pre-wrap; white-space: -pre-wrap; white-space: -o-pre-wrap; word-wrap: \
break-word;">see summary. Makes animations smoother and would have prevented RR \
http://git.reviewboard.kde.org/r/103733 ;-)
I'll keep it in my personal 4.8 branch and therefore won't care about whether \
it's applied to 4.8.n or 4.9 :-P</pre> </td>
</tr>
</table>
<h1 style="color: #575012; font-size: 10pt; margin-top: 1.5em;">Testing </h1>
<table width="100%" bgcolor="#ffffff" cellspacing="0" cellpadding="10" style="border: \
1px solid #b8b5a0"> <tr>
<td>
<pre style="margin: 0; padding: 0; white-space: pre-wrap; white-space: \
-moz-pre-wrap; white-space: -pre-wrap; white-space: -o-pre-wrap; word-wrap: \
break-word;">generic animations still work - better ;-)</pre> </td>
</tr>
</table>
<h1 style="color: #575012; font-size: 10pt; margin-top: 1.5em;">Diffs</b> </h1>
<ul style="margin-left: 3em; padding-left: 0;">
<li>kwin/client.cpp <span style="color: grey">(520ed85)</span></li>
<li>kwin/composite.cpp <span style="color: grey">(55a7144)</span></li>
<li>kwin/effects.h <span style="color: grey">(f4ad2fb)</span></li>
<li>kwin/effects.cpp <span style="color: grey">(6c252c9)</span></li>
<li>kwin/events.cpp <span style="color: grey">(26e0139)</span></li>
<li>kwin/toplevel.h <span style="color: grey">(693e6f3)</span></li>
<li>kwin/toplevel.cpp <span style="color: grey">(ffe7f0c)</span></li>
</ul>
<p><a href="http://git.reviewboard.kde.org/r/103742/diff/" style="margin-left: \
3em;">View Diff</a></p>
</td>
</tr>
</table>
</div>
</body>
</html>
_______________________________________________
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]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic