View Single Post
Old 04-03-2008, 01:14 PM   #175
HarryT
eBook Enthusiast
HarryT ought to be getting tired of karma fortunes by now.HarryT ought to be getting tired of karma fortunes by now.HarryT ought to be getting tired of karma fortunes by now.HarryT ought to be getting tired of karma fortunes by now.HarryT ought to be getting tired of karma fortunes by now.HarryT ought to be getting tired of karma fortunes by now.HarryT ought to be getting tired of karma fortunes by now.HarryT ought to be getting tired of karma fortunes by now.HarryT ought to be getting tired of karma fortunes by now.HarryT ought to be getting tired of karma fortunes by now.HarryT ought to be getting tired of karma fortunes by now.
 
HarryT's Avatar
 
Posts: 85,557
Karma: 93980341
Join Date: Nov 2006
Location: UK
Device: Kindle Oasis 2, iPad Pro 10.5", iPhone 6
Quote:
Originally Posted by tompe View Post
Yes, but a reasonable explanation is that is beacuse they only have implemented what is easy to implement. And if the write there own reader and only use support functions from MobiPocket tey can implement whatever they want so you cannot blame or explain the implementation by saying that they have only licensed the code which was what you did above.
They have their reader code and they could have implemented something that worked better. Do not blame MobiPocket.
I merely note that the Mobi reader shows page numbering bugs on all platforms. It seems logical, therefore, to acribe this behaviour to the internal functionality of Mobi's code. I could be wrong. You could be wrong. We all could be wrong. Who knows? It's just a guess.
HarryT is offline   Reply With Quote