View Single Post
Old 09-21-2018, 03:30 AM   #5
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: 24,905
Karma: 47303824
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
Quote:
Originally Posted by sv2000 View Post
Thanks for the reply. I must admit this might not be the most well thought out idea. The fmon launcher icon gets buried beneath other books I read in nickel and I don't think there's a way to pin it to the home screen. Minor inconvenience, but I'm just starting to tinker with my Kobo Glo HD, and this was the first thing which came to my mind.
The books on the home screen are all books being read with in order of most recently read. You could put a book to the first location on the home screen by setting the last read date to sometime in the future and setting the appropriate status. But, as soon as you opened the book, these would change. And I suspect that the fmon icon gets marked as read when it is opened. But, you could use a database trigger to do it.

Something like the following should do it:

Code:
CREATE TRIGGER PinFMonOnHome
AFTER UPDATE ON content
  FOR EACH ROW
  WHEN ContentID = 'file:///mnt/onboard/path_to_the_icon'
  AND ContentType = 6
BEGIN
  UPDATE content 
  SET DateLastRead = '2222-01-01T00:00:01Z, ReadStatus = 1
  WHERE rowid = new.rowid;
END
I haven't tested that. I'm working partly from memory and partly from looking at other examples I have posted here before and are in my Kobo Utilities plugin. I'm not going to guarantee that I have the syntax correct. But, it should be pretty close.

There is also a timing issue. While the books on the home screen are based on the ReadStatus and DateLastRead, it is possible that the database isn't always used. The device maintains the data in memory, so that it doesn't have to constantly reread the database. A trigger like this might only work when the device is turned on. Or it might work when you return to the home screen from the lists. It won't surprise me too much if when you finished a book, it didn't work but the next time the home screen was refreshed, that the book reappeared.

If you want to try this, take a copy of the database first. I might try it when I get home using one of my other devices. I'm not going to break my Clara HD just before my commute home
davidfor is offline   Reply With Quote