Quote:
Originally Posted by dpavlin
If I understand you correctly, you would expect to be able to move through columns using previous and next page buttons instead of fiveway (I haven't used Duokan, so I might be wrong)
I though about it while implementing this feature, and somehow I decided that depending on human interaction seems more logical to me than having to specify number of columns. Current implementation works equally well for any number of columns if you zoom to first one manually since it depends on direction in which fiveway is pressed.
Then, when playing with a reader on real device, I somewhat liked using page previous/next to quickly browse through book, and though that it's somewhat more logical since keys behave same in each zoom mode.
I can be persuaded otherwise, but that would require code change and some way to specify number of columns so we can build matrix of all available position on page. Downside of that is that sometimes you have parts of page in which you are not interested (ads for example) which you can quickly skip using page buttons in current implementation.
|
dpavlin, Thanks for your answer.
Yes, you uderstand me almost correctly (almost because pagetirning in one column horizontal (album) orientation differs from 2-column mode).
More people read books(or pieces of books) from begin to end page by page
How is pageturning (I mean actions for move to next piece of text) realized now:
- in one column vertical orientation to see next piece of text user must press PageDn. It's Ok
- in one column horizontal (album) orientation reader shown upper piece of page, and to see lower piece page user must hold pressing fiveway down some time (2-3s) for very slow scroll down
- in 2-column mode regardless to orientation to see next piece of text user must press fiveway down and when he go to end of page must press fiveway right. How it's look at reading: down(fiveway); down; down;
Oh no, not response for pressing down must press right, down, down etc... It's not too comfortable as for me.
I wish that in al all this modes to see next text piece it will be enough to press PageDn only. The function that go to next page regardless to current mode (like PageDn now) is usefull too, but it's using rarely, and it's logical to correspond to this functions any 2 keys of keyboard. It's will be great if the user will be have opportunity to change functions of keys as he wish, for example in txt file.
Multicolumn mode is very usefull. It will be great if you mke it
Bugreport: if you change orientation in 90 degrees by ^J,k and after that goes to screensaver, it's orientate so screensaver picture too. If it was horizontal orientation screensaver picture becomes corrupt (blur and multiple). When you switch on, the home screen is corupt the same too.
It's important, how screensaver starts. If by swith off - it's enough to pageturn or joystick press to return to kpdfreader. If by timeout - hard reset helps only. Please debug it.