Thread: "In device" check not properly refreshed with latest versions
View Single Post
Old 08-02-2012, 11:13 PM   #7
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 theducks View Post
Calibre Looks at your Device
If your device has the Book and/or the OPF file, Calibre considers it is on Your device

This does not make it a calibre problem.... It makes it a garbage collection problem.
As there are no OPF files at all on my Kobo Touch device, and the book has been deleted from the file structure on the device and the appropriate records have been deleted from the SQL database on the device, that makes me think that calibre is not refreshing something somewhere.

Another test: If I exit calibre and come back in, then the display is correct. That was done without disconnecting the device. That means that it is calibre not doing something to refresh the original display. As I said earlier, my guess is that something was changed elsewhere that the Kobo device driver hasn't been updated to reflect.

Hmm, the other possibility is that the recent change in the device driver to test the firmware version and use an option to ignore this is not working correctly. It is called at the start of a lot of methods and I haven't looked at all of them to see if there might be one that is different somehow. If someone with a calibre version from before check was added can check what happens, then we can eliminate/confirm this. At the least it will help determine when this started happening.
davidfor is offline   Reply With Quote