<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/106789/">http://git.reviewboard.kde.org/r/106789/</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 13th, 2012, 5:43 p.m., <b>Greg T</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'm quite satisfied with the keyboard handling after applying your patch.
some notes:
- when I press key up/down at the top/bottom of a flippscroll view, the launcher jumps back to the favourite view. I think it should just stay in the current view.
- key_tab moves the keyboard focus around, away from the searchbar. Can you suppress that?</pre>
</blockquote>
<p>On October 13th, 2012, 10:50 p.m., <b>Richard Stockton</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;">Note 1:
I first tried to keep the applicationView/flipScrollView visible (upon and Up/Down at the Top/Bottom of flipScrollView), but I kept creating nasty loops of focus between the SearchView and ApplicationsView. Different problems for the first column versus other columns... with and without a 3rd layer of children... and different for Left-To-Right and Right-To-Left tabs, too.
I can hack it as another usability bug, with this as Pre-Requisite. It would possibly involve changing appViewIsReceivingKeyEvents from bool to int, and letting it increment (with notReceiving behavior on even values, receiving behavior on odd values, and a new bool to detect and correct looping). Or, I could change the order of key event interpretation in the filter... again ... but that's dangerous.
I'd like to get this done as-is first, because THIS problem is major. If you agree, then I'll open that new usability bug and assign to myself, still for 4.9 (2 weeks). We both agree that my new behavior is awkward, although it's (at least) quite clear that I've moved your View in a fundamental way.
Note 2:
key_tab moves focus around in all instances of QAbstractItemView (which is the parent of all the contentArea views). This would constitute a change of behavior, and I'd also like to leave those other classes alone. (I'm not very good at this, I'd probably break it).
</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;">This is fine by me, since rev r8 is a fundamental improvement. Just address those 2 issues and we are good to go.</pre>
<br />
<p>- Greg</p>
<br />
<p>On October 13th, 2012, 4:19 a.m., Richard Stockton 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 Plasma and Greg T.</div>
<div>By Richard Stockton.</div>
<p style="color: grey;"><i>Updated Oct. 13, 2012, 4:19 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;">Fix regression (keyboard usage) introduced in Kickoff-Widget 4.9.2</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;">Navigation of single-column Views, and execution of selected items.
Navigation of "All Applicatons" flipScrollView, and execution of endpoint (child-less) items.
Return to "SearchBar" from within all Views. (Key_Up and Key_Down work in many situations, but not all situations of flipScrollView. Key_Tab always works, although it often needs to be pressed twice. Breadcrumb often receives focus after the first Key_Tab.)
Navigation and execution of selected items in all View "Tabs", after having returned focus to searchBar from within flipScrollView and other Views.</pre>
</td>
</tr>
</table>
<div style="margin-top: 1.5em;">
<b style="color: #575012; font-size: 10pt; margin-top: 1.5em;">Bugs: </b>
<a href="http://bugs.kde.org/show_bug.cgi?id=307823">307823</a>
</div>
<h1 style="color: #575012; font-size: 10pt; margin-top: 1.5em;">Diffs</b> </h1>
<ul style="margin-left: 3em; padding-left: 0;">
<li>plasma/desktop/applets/kickoff/ui/flipscrollview.h <span style="color: grey">(bf12b9c)</span></li>
<li>plasma/desktop/applets/kickoff/ui/flipscrollview.cpp <span style="color: grey">(98bc0bd)</span></li>
<li>plasma/desktop/applets/kickoff/ui/launcher.h <span style="color: grey">(0c3c5c8)</span></li>
<li>plasma/desktop/applets/kickoff/ui/launcher.cpp <span style="color: grey">(3d85688)</span></li>
<li>plasma/desktop/applets/kickoff/ui/searchbar.cpp <span style="color: grey">(ab47302)</span></li>
</ul>
<p><a href="http://git.reviewboard.kde.org/r/106789/diff/" style="margin-left: 3em;">View Diff</a></p>
</td>
</tr>
</table>
</div>
</body>
</html>