[odamizu]

Originally Posted by ShellShock

... For example:

• Start in landscape: "6 pages left in This section".
• Rotate to portrait: "Last page in This section".
• Rotate to landscape: "10 pages left in This section".

It now settles down between last page (portrait) and 10 pages left (landscape). We can see that the difference in location is not minor: as much as 10 pages in this example, which can make finding your last reading position quite tricky.

YES! This isn't a matter of flipping back or forth a screen or two to find your place. The fact that you can't even count on finding your place again by switching back to the previous orientation is even more frustrating.

Originally Posted by Turtle91

Yes, Kris is aware of this issue. It was found during Beta testing and discussed a bit. Part of the problem is that there is no way to determine where on the current screen your eyeballs are looking when you decide to flip orientation. The best any programmer could do is to assume they were on the first paragraph/sentence displayed in that view and then cause that paragraph/sentence to be at the top after rotation.

This isn't what's happening in my experience. If it were simply a matter of being taken back to the first paragraph/sentence displayed before the change in rotation, I'd be okay with that. But the change in location is so great that I've given up trying to find my place after flipping back and forth 10+ screens.

Also, no other app I've used has this problem, including Kindle for iOS, Hyphen, MapleRead, Bluefire Reader. So some programmers have clearly figured out how to make this work.

... I imagine, Kris put this as a lower priority than some other ideas he is working on that would actually have a solution that people will be happy with.

In the meantime, my recommendation to avoid getting caught out is to rotate the orientation at the beginning of a chapter/file. You will not lose your position because there is no "reflow error". Also, you can manually select and lock the orientation instead of letting it auto-switch. You won't ever have it switch accidentally.

Actually, my solution has been to abandon Marvin 3 in favor of other switch to another ereading app that doesn't have this bug but still offers the features I'm looking for. I'm dismayed to hear that Kris likely considers this low priority and not worth fixing.