<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="https://git.reviewboard.kde.org/r/118232/">https://git.reviewboard.kde.org/r/118232/</a>
</td>
</tr>
</table>
<br />
<blockquote style="margin-left: 1em; border-left: 2px solid #d0d0d0; padding-left: 10px;">
<p style="margin-top: 0;">On May 21st, 2014, 8:15 a.m. UTC, <b>Camilla Boemann</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 think it's safe enough to commit this, however in the text tool every botton emits an i_am_done signal which we use to return focus to the canvas. Some widgets will keep the focus (and we would want them to be navigatable by keyboard for accessability) and without this signal it wont work
just some inspiration for testing and further improvement.
That said i'll say ship it but please check that text input widget (like font selector in text tool) still works</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;">Ah, I was wondering how other apps dealt with this, yes something like that would work too, and might indeed be better from the keyboard navigation point of view...
Font selectors still seem to work just fine.</pre>
<br />
<p>- Marijn</p>
<br />
<p>On May 20th, 2014, 11:42 p.m. UTC, Marijn Kruisselbrink wrote:</p>
<table bgcolor="#fefadf" width="100%" cellspacing="0" cellpadding="8" style="background-image: url('https://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 Calligra.</div>
<div>By Marijn Kruisselbrink.</div>
<p style="color: grey;"><i>Updated May 20, 2014, 11:42 p.m.</i></p>
<div style="margin-top: 1.5em;">
<b style="color: #575012; font-size: 10pt;">Repository: </b>
calligra
</div>
<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;">Currently everytime you click a button to change formatting of a cell in sheets the scrollarea gets keyboard focus, making further editing very annoying. This fixes that behavior.
I'm not sure if any other code/UI depends on this scroll area being focusable though?
(two years ago I made the same change in 5e2cc2ee27a50806b0c2eb16724ad704a6450d9f for KoToolDocker)</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>libs/main/KoModeBox.cpp <span style="color: grey">(91f71e2)</span></li>
</ul>
<p><a href="https://git.reviewboard.kde.org/r/118232/diff/" style="margin-left: 3em;">View Diff</a></p>
</td>
</tr>
</table>
</div>
</body>
</html>