View Single Post
Old 11-22-2018, 08:31 AM   #41
davidfor
Grand Sorcerer
davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.
 
Posts: 19,068
Karma: 32762907
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
Quote:
Originally Posted by geek1011 View Post
and the second one is nearly impossible due to the same reason (but I might be able to do some changes where it actually updates that list).
That one is a little frustrating. It can almost be done with a database trigger. You just need to set the last read timestamp to the future and set the reading status to reading. But, because nickel is using in-memory structures, it uses the status it set the book to until the next time it rereads the status from the database. So you open the image, it gets marked as finished but the trigger intercepts the database update. The image disappears from the home page, but if you connect to the PC, the image reappears on the home page.

If KOReader could be triggered from something other than an image, it might work as other formats are not automatically marked as read when opened.
davidfor is offline   Reply With Quote