View Single Post
Old 01-12-2012, 03:39 PM   #114
pruss
Evangelist
pruss ought to be getting tired of karma fortunes by now.pruss ought to be getting tired of karma fortunes by now.pruss ought to be getting tired of karma fortunes by now.pruss ought to be getting tired of karma fortunes by now.pruss ought to be getting tired of karma fortunes by now.pruss ought to be getting tired of karma fortunes by now.pruss ought to be getting tired of karma fortunes by now.pruss ought to be getting tired of karma fortunes by now.pruss ought to be getting tired of karma fortunes by now.pruss ought to be getting tired of karma fortunes by now.pruss ought to be getting tired of karma fortunes by now.
 
Posts: 461
Karma: 819417
Join Date: Nov 2004
Quote:
Originally Posted by HarryT View Post
It's a "feature" of Mobipocket that a page back doesn't exactly "undo" a page forward. It's the way it's always worked, right back to the earliest Mobi readers, which were a heck of a long time before the Kindle was a twinkle in Amazon's eye.
I guess it's not a bug, but a carry-over of what was a reasonable design decision on an early Palm with limited memory, but is no longer a reasonable design decision.

On a limited memory device there is going to be a choice between limited memory one will have a trade-off between slow paging, at least in reverse, and unpredictable reverse paging. In Plucker, the issue was solved differently, at the cost of slow paging both forwards and backwards in documents with large paragraphs and some additional memory use.

On a modern device with oodles of RAM (all Kindles have oodles of RAM by the standards of early Palms), this is a poor design decision. One wants to be able to find the exact place one was reading more easily when one jumps to a footnote or forward and then comes back.
pruss is offline   Reply With Quote