<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/105229/">http://git.reviewboard.kde.org/r/105229/</a>
</td>
</tr>
</table>
<br />
<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 review has been submitted with commit 7d5c6428d73bcd46d0e54b0128dd5e3d3231ab64 by Friedrich W. H. Kossebau to branch master.</pre>
<br />
<p>- Commit</p>
<br />
<p>On June 14th, 2012, 4:12 p.m., Friedrich W. H. Kossebau 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 Calligra, Yue Liu and Thorsten Zachmann.</div>
<div>By Friedrich W. H. Kossebau.</div>
<p style="color: grey;"><i>Updated June 14, 2012, 4:12 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;">I found that I sometimes would like to scroll the pages with the status bar page navigator.
So this patch adds support for switching the pages with wheel events.
It makes the page navigator behave similar to a vertical scroll bar (so not like a normal integer editor),
as it seems similar in the UI concept to me:
* control buttons on the left and right (not up/down)
* page number like a representative/symbol of the current page, and pages are ordered with lower page numbers first
This way it feels more natural to me (had it first differently).
But there are some things I am not decided about:
* should the wheel events also be dealt with if the mouse hovers the buttons?
* proper behavior in Right-to-left environment is?
* what to do if the page editor has focus?
a) ignore wheel event
b) exit edit mode (dropping any changes), then scroll as in display mode
c) take current edited number, exit edit mode, select page, then scroll as in display mode
d) change the edited number and stay in edit mode, but do not activate a page
e) change the edited number and stay in edit mode, activate the page with the number
Implemented is currently b), because it felt to me better and more consistent.
Currently only on pressing Enter an edited number is picked up, set respective page selected and the editor left.
Why would one start enter a new number and then switch to use the mouse wheel? Switching to the wheel is more like
cancelling the editing mode, not continuing.
What is your opinion?</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;">Scrolled with a few slides, with and without page number editing mode.</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/kopageapp/widgets/KoPageNavigator.cpp <span style="color: grey">(2ecdc9a)</span></li>
<li>libs/kopageapp/widgets/KoPageNavigatorButton_p.h <span style="color: grey">(f7fdc26)</span></li>
</ul>
<p><a href="http://git.reviewboard.kde.org/r/105229/diff/" style="margin-left: 3em;">View Diff</a></p>
</td>
</tr>
</table>
</div>
</body>
</html>