View Single Post
Old 07-28-2016, 07:19 AM   #6
chaley
Grand Sorcerer
chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.
 
Posts: 12,465
Karma: 8025600
Join Date: Jan 2010
Location: Notts, England
Device: Kobo Libra 2
Quote:
Originally Posted by davidfor View Post
I haven't seen a mechanism to do what you want. It could be written as a plugin, but it would need either the drivers for the device to collect the timestamp info, or for the plugin to get the timestamp directly from the device. I don't remember if any of the drivers do the former, and the latter might need something written for each device.
The "synchronize_with_db" device interface method can be used to do this. CC (Calibre Companion) uses it for this purpose as well as for syncing some information from the device into calibre's database.

CC does the job by collecting the timestamp information from the device during the scan phase. These timestamps are compared to the files in the calibre library during the book matching phase, which is when synchronize_with_db is called. If the calibre file is newer then CC asks calibre to send the book.
chaley is offline   Reply With Quote