View Single Post
Old 10-01-2018, 09:34 AM   #567
stumped
Wizard
stumped ought to be getting tired of karma fortunes by now.stumped ought to be getting tired of karma fortunes by now.stumped ought to be getting tired of karma fortunes by now.stumped ought to be getting tired of karma fortunes by now.stumped ought to be getting tired of karma fortunes by now.stumped ought to be getting tired of karma fortunes by now.stumped ought to be getting tired of karma fortunes by now.stumped ought to be getting tired of karma fortunes by now.stumped ought to be getting tired of karma fortunes by now.stumped ought to be getting tired of karma fortunes by now.stumped ought to be getting tired of karma fortunes by now.
 
Posts: 3,305
Karma: 10259306
Join Date: May 2016
Device: kobo forma, Kobo Libra, Huawei media Tab, fire HD10, PW3 HDX8.9,
it would not be an " update" it would be a backward step, IMHO, to adopt a different , static page definition

surely the moon+ author is entitled to make a deliberate design choice: that in his app a " page" =" a single full screen of the device in use with the current font, margin etc settings."
why shoudl he have to "update" to what i think is in inferior definition of " page" , based on an arbitrary character count ; that definition, as used in adobe based renderers leads to the silly situation where a "page" goes on for 3 3/4 screens, then changes part way through screen 4. how is that better? I like seeing how many more screens will take me to a chapter end.

"page" is a paper book concept, "screens" is a better thing to count , and that is what moon+ counts, one chapter at a time
ok so a side effect of Moon's choice is that you cannot see the number of (adobe definition ) "pages" in a book in the screen footer. That's the trade off, and those who simply must see that at on every screen are welcome to use a different reader app.
stumped is offline   Reply With Quote