Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
[Kobo] Restart KOReader after a crash #5328
Not so fond of the idea, but may be that's because I'm a dev - while users may like it.
Additionally, depending on what I suspect caused the crash (if I'm testing stuff), I do not want to restart koreader. Possibly because then I would just be waiting 15s before being able to get back to usb, and it would fill crash.log with multiple instances of the crash.
I'll probably patch that out for my own safer usage (may be you could make that an option ? in developpers options?).
(But may be I'd like a 1-time restart, with an excerpt of the crash log stacktrace on your grey screen :) so I know what next step to take: restart or go fix that over usb :)
@Frenzie: That's exactly what this does ^^ (except with a 5s grace period instead of 10 ;p). Plus, any "expected" exit (i.e., a KOReader restart via the menu) will reset the counter.
@poire-z: The idea behind the 5 (well, in practice, 6) crash limit is to avoid getting stuck in a loop in the unlikely event we crash on startup.
The vast majority of crashes do NOT happen on startup, though, and in 99% of thoses cases, you will probably end up restarting KOReader straight away ;).
That said, I do get the point about wanting to just die on crash as usual, I'll look into it ;).
There are a few other fun icons available, FWIW.
I settled with the bomb because it made me laugh, and (somehow, despite me barely ever having used a classic Mac) reminded me of the old Mac OS system error popup...
In the same vein, there's a "Fire" icon, which could be a nod to HCF/Halt and Catch Fire.
Or less nerdy stuff like skull & bones or something ;p.