View Single Post
Old 02-20-2025, 04:11 PM   #9
JSWolf
Resident Curmudgeon
JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.
 
JSWolf's Avatar
 
Posts: 79,983
Karma: 147448039
Join Date: Nov 2006
Location: Roslindale, Massachusetts
Device: Kobo Libra 2, Kobo Aura H2O, PRS-650, PRS-T1, nook STR, PW3
Quote:
Originally Posted by inker View Post
That "resume" file must be:

- Created when you power down
- KOReader actually should create it by intercepting the power down
- Deleted after a resume

Now, if KOReader is frozen, no interception, no creation.

Another approach would be to ask the user if they want to resume when such file exists. This whole resume "feature" can be guarded by a non-default option.

I have to say, I've never ended up in a frozen loop with my other device though.
That won't work. Sure KOReader could create a restore file (if programmed to do so), but Nickle (Kobo's software) will know nothing about it or how to use it.
JSWolf is offline   Reply With Quote