Quote:
Originally Posted by kpw
Hi ThR,
Although this plugin doesn't do any updates to collections in the device, I think I can see a situation where the data I'm working with could get out of sync with the data on the device, and you could end up with something like you're describing.
I do a check when the action is invoked to make sure there are no device tasks running in the background in an atempt to avoid working on stale metadata. But I've just been able to verify that, if I time it right, I can get the action to start up just before the device metadata update task starts after Calibre detects the device. That would probably end up with my plugin making its updates to the book timestamps using stale cache.xml/media.xml content.
I'll put in a check to make sure this doesn't happen.
Does it sound like this might be the scenario you're running into?
|
I'm not sure. I started the plugin after I'd checked, that calibre was doing nothing (tasks in the queue were finished). On the device itself, I could not see somethings running.
When I reconnect the device after running your plugin, calibre adds all collections back again and everything is fine.
But I found another error: the reading history was deleted too, so the reader wanted me to start reading with page 1 instead of 253, where I ended my last reading session.