Closed GoogleCodeExporter closed 9 years ago
Just tried described scenario. Not reproduced.
Possible it is issue of your hardware.
Original comment by Andrei.K...@gmail.com
on 1 Oct 2011 at 9:08
This problem sometimes occured on Pocketbook IQ 701 at earliest versions of
program, and I always thought that it's screen calibration fault, because after
I did calibration one more time bug immediately disappeared.
Original comment by Ola...@rambler.ru
on 2 Oct 2011 at 7:29
Ok. I got this one time on hardware, but can not reproduce this on emulator in
debug mode. We will try to fix this as soon as we get how to reproduce it.
Original comment by Andrei.K...@gmail.com
on 2 Oct 2011 at 10:33
Funny thing, I saw this a dozen times since starting using EBookDroid (in
"natutal conditions"). Today I sat to describe exact steps to reproduce and see
that yes, it's rather non-deterministic.
Original comment by pmis...@gmail.com
on 5 Oct 2011 at 7:29
Ok, here we go:
And here's my transcript on reporoducing it:
1. Download http://www.linuxformat.ru/download/125.pdf (no, it happens with
others too, just to be specific)
2. Copy it to device. This is completely new file, not know to EBookDroid yet.
3. Open it in EbookDroid (on page 1 consequently)
4. Fast scroll to page 10
5. Open menu, select "Go to page"
6. Using slider in dialog, set page to 40. Click "Go to page button" in dialog.
7. Observe position stays at page 10
8. Open "Go to page" dialog again, step 6 again.
9. Observe it went to page 40.
10. Close EBookDroid, open again, try steps 3-9 again (using different page
numbers), observe they're reproducible 100%.
Crucial step appears to 4 - scrolling thru pages, that's why I saw the issue
many times.
My settings are:
Memory usage:
Pages in memory: 0
Memory usage mode: Normal page slices
Rendering mode:
Split pages: Off
Single page mode: Off
Touch scroll: Off
Original comment by pmis...@gmail.com
on 5 Oct 2011 at 7:37
Just tried with Pages in memory: 1 - happens too.
Original comment by pmis...@gmail.com
on 5 Oct 2011 at 7:39
Original comment by Alexander.V.Kasatkin@gmail.com
on 16 Dec 2011 at 1:54
Original issue reported on code.google.com by
pmis...@gmail.com
on 1 Oct 2011 at 8:39