View Single Post
Old 12-08-2018, 07:18 PM   #16
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 compurandom View Post
So with this update, I now have a virtual book showing up in the device tab.
I can't delete it, and it shows up in the calibre device view both with all checked and all unchecked under metadata / show as on device.

I actually don't care that it shows up; what I care is that it now triggers smart eject to show there's a book on my device that isn't in the library, and I can't seem to figure out how to exclude it. I tried "size:=0" but that doesn't match it.

So, how can I exclude this virtual book in the device view (without excluding real ones), and/or what can I do to help debug where this came from, since it doesn't seem to be a recommendation, archived book, or preview (or at least, unchecking those boxes doesn't make it go away).
To do the metadata updating, I did rework a lot of code in the driver. But, it shouldn't have changed anything related to what books are seen on the device. To let me see what is happening, in the driver configuration, put the name of the errant book in the "Title to test when debugging" field on the third tab. It doesn't need to be the full title, just something that will match the book without matching to many others (i.e. don't use "the"). Then run calibre in debug mode, let the device connection jobs run and then close calibre. Then post or PM the complete log to me.

Quote:
Originally Posted by compurandom View Post
Also, I have a template in update metadata -> comments that the new driver update is not using and clears on the device, so I've disabled the metadata update in the driver for now... if this could be fixed, it would save me a step when adding new books!
See my answer to @anacreon about the comments and the metadata plugboard.
davidfor is offline   Reply With Quote