<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/112231/">http://git.reviewboard.kde.org/r/112231/</a>
</td>
</tr>
</table>
<br />
<blockquote style="margin-left: 1em; border-left: 2px solid #d0d0d0; padding-left: 10px;">
<p style="margin-top: 0;">On August 24th, 2013, 11:51 a.m. MSK, <b>Vlas Puhov</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;">When in debug mode:
there is only two actions:
stop all jobs
back to code.
What if I want to stop only the current debug job?
When I choose "back to code" from debug mode how can I return to it afterwards??
I think in code mode should be a button like this: "back to debug". Or remove "back to code" action in the first place.
Also notice, that disassemble/registers toolview not cleared after debug session ended, so it still keeps useful information. I think it'd be a great thing if we could have access to it too.</pre>
</blockquote>
<p>On August 25th, 2013, 3:08 a.m. MSK, <b>Aleix Pol Gonzalez</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;">You can go to Run > Stop > job to stop.
Either way, I don't really see how this relates... You'll keep having the same tools you used to have only that they'll be flow-based instead of explicit by the user.</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;">Yeah, I understand that tools'll stay the same. What I was trying to say is: When in debug mode if you want to stop something it probably the current debug launch not, let's say background parsing. So, IMO there should be the one and only button like: "stop current debug launch".</pre>
<br />
<p>- Vlas</p>
<br />
<p>On August 24th, 2013, 3:06 a.m. MSK, Aleix Pol Gonzalez wrote:</p>
<table bgcolor="#fefadf" width="100%" cellspacing="0" cellpadding="8" style="background-image: url('http://git.reviewboard.kde.org/static/rb/images/review_request_box_top_bg.ab6f3b1072c9.png'); background-position: left top; background-repeat: repeat-x; border: 1px black solid;">
<tr>
<td>
<div>Review request for KDevelop.</div>
<div>By Aleix Pol Gonzalez.</div>
<p style="color: grey;"><i>Updated Aug. 24, 2013, 3:06 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;">The area switching tabs is something that has bothered me quite a bit recently. It's something that is always visible in the screen and we barely use it. There's very little point to explicitly changing to an area, we usually do it from an action: debug, show differences, etc. These are specified by a new Area::addAction(QAction*) method.
This patch changes the current tab interface (inspired from Eclipse IIRC), for a button that tells the user what's the current area and where we can go.
The patch also removes the tabs and some unneeded abstractions in sublime/mainwindow that where only used by the tabs.</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;">Been using it for a couple of days, seems safe.</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>shell/CMakeLists.txt <span style="color: grey">(fe5cd9b)</span></li>
<li>shell/areadisplay.h <span style="color: grey">(PRE-CREATION)</span></li>
<li>shell/areadisplay.cpp <span style="color: grey">(PRE-CREATION)</span></li>
<li>shell/mainwindow.h <span style="color: grey">(2050219)</span></li>
<li>shell/mainwindow.cpp <span style="color: grey">(d4f4bcb)</span></li>
<li>shell/projectcontroller.cpp <span style="color: grey">(2186d90)</span></li>
<li>shell/runcontroller.cpp <span style="color: grey">(4a5a5e4)</span></li>
<li>shell/uicontroller.cpp <span style="color: grey">(2c0400f)</span></li>
<li>sublime/area.h <span style="color: grey">(878c120)</span></li>
<li>sublime/area.cpp <span style="color: grey">(df29ce3)</span></li>
<li>sublime/mainwindow.h <span style="color: grey">(96b9e71)</span></li>
<li>sublime/mainwindow.cpp <span style="color: grey">(f405200)</span></li>
<li>sublime/mainwindow_p.h <span style="color: grey">(7885d06)</span></li>
<li>sublime/mainwindow_p.cpp <span style="color: grey">(23c638d)</span></li>
</ul>
<p><a href="http://git.reviewboard.kde.org/r/112231/diff/" style="margin-left: 3em;">View Diff</a></p>
<h1 style="color: #575012; font-size: 10pt; margin-top: 1.5em;">File Attachments </h1>
<ul>
<li><a href="http://git.reviewboard.kde.org/media/uploaded/files/2013/08/23/pairs-credits2.png">pairs-credits2.png</a></li>
<li><a href="http://git.reviewboard.kde.org/media/uploaded/files/2013/08/23/pairs-credits2_1.png">pairs-credits2_1.png</a></li>
<li><a href="http://git.reviewboard.kde.org/media/uploaded/files/2013/08/23/pairs-credits2_2.png">pairs-credits2_2.png</a></li>
</ul>
</td>
</tr>
</table>
</div>
</body>
</html>