<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/106722/">http://git.reviewboard.kde.org/r/106722/</a>
</td>
</tr>
</table>
<br />
<blockquote style="margin-left: 1em; border-left: 2px solid #d0d0d0; padding-left: 10px;">
<p style="margin-top: 0;">On October 4th, 2012, 1:15 p.m., <b>Alex Fiestas</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;">Mmm so I won't be able to trigger any edge while watching a video in fullscreen? on my laptop (with one screen) that's one of the things I do most :/
For a video, a presentation, and even file browser there are not many chances of the user hitting an edge accidentally... There is a problem with applications that have a custom GUI like gwenview on which case we may want to disable them (I'm still unsure but anyway).
I feel that screen edges is something we haven't stop thinking of how the user may use'em if at all. In OSX by default they are NOT configured. If a user configure them manually we can assume that the user is "mature enough" to handle fullscreen app's and screen edges.</pre>
</blockquote>
<p>On October 4th, 2012, 1:25 p.m., <b>Martin Gräßlin</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;">config option?</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;">Config option for what exactly?
I think the decision we take on this mostly depends on how we intend the user to use screen edges.</pre>
<br />
<p>- Alex</p>
<br />
<p>On October 4th, 2012, 1:02 p.m., Martin Gräßlin 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, Plasma and Aurélien Gâteau.</div>
<div>By Martin Gräßlin.</div>
<p style="color: grey;"><i>Updated Oct. 4, 2012, 1:02 p.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;">Block screen edge activation for fullscreen windows
If the active client is a fullscreen window, the screenedges on the
screen the window is on get's blocked for activation.
We have to assume that the window is managing the screenedge itself to
offer there additional functionality (e.g. a panel) and KWin's screen
edge functionality would conflict.</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/screenedge.cpp <span style="color: grey">(a1507c3543877477e564bba368feaa31bc44655e)</span></li>
</ul>
<p><a href="http://git.reviewboard.kde.org/r/106722/diff/" style="margin-left: 3em;">View Diff</a></p>
</td>
</tr>
</table>
</div>
</body>
</html>