Quote:
Originally Posted by Oleksa
Main issue is normal pageturning in modes that differs from vertical one page mode (2-column). Now pageDn pressing leads to move to next page regardless to present mode. It's very uncomfortable in horizontal orientation and 2-column mode. Issue is that pageDn pressing leads to move to next text piece not to next page (like in Duokan)
|
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.