Quote:
Originally Posted by inker
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.
|
You just haven't had a suitably bad ebook yet.
Not even on Windows, or any *inx (if you set to reload open windows on *inx)?