Quote:
Originally Posted by howyoudoin
But it is simple, isn't it?
They already have an algorithm that recalculates pages left in chapter based on your font size, margin and line spacing settings. All they need to do is extend that algorithm to span pages left in the entire book too. Seems simpler than using different algorithms for chapter and entire book.
|
The problem is that they would have to load all of the (remaining) chapters and calculate the page count for each one each time a book is opened or the settings are changed. On a device as slow as an e-ink reader, that delay would be significant. (Multiply the time it takes to change to the next chapter by the appropriate number of chapters.)
The reason that the alternate algorithm for calculating the "incorrect" number of pages for the entire book is so fast is that it simply reads the size of the remaining compressed chapter files in bytes and divides by 1024. It doesn't have to load the files themselves.