View Single Post
Old 01-30-2010, 07:21 PM   #174
Jim Chapman
Addict
Jim Chapman ought to be getting tired of karma fortunes by now.Jim Chapman ought to be getting tired of karma fortunes by now.Jim Chapman ought to be getting tired of karma fortunes by now.Jim Chapman ought to be getting tired of karma fortunes by now.Jim Chapman ought to be getting tired of karma fortunes by now.Jim Chapman ought to be getting tired of karma fortunes by now.Jim Chapman ought to be getting tired of karma fortunes by now.Jim Chapman ought to be getting tired of karma fortunes by now.Jim Chapman ought to be getting tired of karma fortunes by now.Jim Chapman ought to be getting tired of karma fortunes by now.Jim Chapman ought to be getting tired of karma fortunes by now.
 
Posts: 310
Karma: 2025434
Join Date: Oct 2009
Device: Lumia 950 Phone
Quote:
Originally Posted by chaley View Post
I have Freda set up to reopen the last book when it starts. I am not changing the screen orientation or window mode. When I do reopen the book, Freda rapidly displays the page I was on, waits a few seconds, then shifts into 'loading...', during which time I can do nothing. When loading finishes, it starts repaginating, which can take minutes.

The same thing happens when I close the book, then immediately reopen it, without closing Freda itself.

Is this behavior expected? I would have thought that closing and reopening the same book wouldn't require significant processing, because the temporary data would be in the cache.
This behaviour is what I would expect. When you first open a book, Freda will (if it was the last book you looked at) put the 'last viewed' page on the screen (it does that by saving the bitmap as a file, so it has it ready).
Next it loads the book into memory and paginates it. Until it's loaded & paginated the current chapter, it displays that 'loading/paginating' message. Once it's done the current chapter, the message goes away and the GUI becomes usable. At this point, Freda sets about loading and paginating all the other chapters (i.e. the non-current ones).

Closing the book does, by design, remove all the temporary data from memory (it is kept in a file, to be reloaded when next you open the book). There is no 'cache' as such - and no good reason to implement one. After all, if you don't want to discard the book data from memory, don't close the book.

Regards,

Jim

Last edited by Jim Chapman; 01-30-2010 at 07:26 PM.
Jim Chapman is offline   Reply With Quote