Quote:
Originally Posted by reuerendo
Thank you  The progress bar reaches 100%. Now using koreader is almost no different from the native reader. Except for one thing.
If you open a book but do not read it (by accident, for example), the library will say “0% read”. And this message cannot be reset.
If you repeat the same steps with the native PocketBook reader, there will be no message in library. It only appears if you scroll through at least one page. And disappears if you return to the first page (book cover) |
Quote:
Originally Posted by liskin
I suppose we could skip updating the progress when the current page is the first one (the cover). But it's not the behaviour I personally want, so it'll probably be best if you tweak that yourself. :-)
|
I dug a bit further into this today to try to find out what exactly does PBReader do. It's really strange actually.
You said the progress bar appears if you scroll through at least one page, but that's not the behaviour I'm seeing—quite often I need to scroll through several, it almost seems like everything until what
Code:
<guide><reference type="text" … /></guide>
refers to is considered "page 0".
But then it also seems that PBReader considers cpage zero-based. If you're on page 5 it sets cpage to 4. But then, if you're on page 60 out of 62, it stores 58. And then 61 is 59, first half of 62 is 60, and when you reach the end it's suddenly 62. It's a bit bizarre. And this behaviour is with an ordinary book with no hidden flows…
We don't really need to replicate that behaviour, though. All we need is to use cpage=0 for the title page (to hide the progress bar), cpage=npage for when the book is finished, and then we can probably map pages 2–(npage-1) to 1–(npage-1) to make the progress bar go smoothly at the beginning of the book (there'd be a slight jump if we went straight from 0 to 2).
I'll implement this and push it to the hidden flows PR at
https://github.com/ckilb/pocketbooks...plugin/pull/10