MobileRead Forums - View Single Post - Calibre 0.8.60

davidfor · 07-18-2012, 11:05 PM

Rob557,

If you have a look at my post in https://www.mobileread.com/forums/sho...d.php?t=185229, you will see that the Kobo Touch hasn't had a firmware version supported by calibre for a while. It still works, but it doesn't take advantage of any new stuff in the KT's database. And if you use bookshelves, data will be left in the KT's database when you delete a book. The message was added in calibre 0.8.60 because the new KT firmware raised the question. As calibre is testing the DBVersion, not the firmware version, putting that in wouldn't have been correct thing. And putting the DBversions in wouldn't give many people any real help (though it would have saved me hunting through the calibre code).

Right now, we have to wait until someone with the time, desire and skill to update the driver for this firmware. Tim Legge said he won't have time have time in the next few weeks. Kovid won't (and rightly so) as he doesn't have one of the devices and he has much more important things to do. If I can wrap my head around the code, I might have a look at it. But it won't be too soon.

07-18-2012, 11:05 PM	#3
davidfor Grand Sorcerer Posts: 24,905 Karma: 47303824 Join Date: Jul 2011 Location: Sydney, Australia Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos	Rob557, If you have a look at my post in https://www.mobileread.com/forums/sho...d.php?t=185229, you will see that the Kobo Touch hasn't had a firmware version supported by calibre for a while. It still works, but it doesn't take advantage of any new stuff in the KT's database. And if you use bookshelves, data will be left in the KT's database when you delete a book. The message was added in calibre 0.8.60 because the new KT firmware raised the question. As calibre is testing the DBVersion, not the firmware version, putting that in wouldn't have been correct thing. And putting the DBversions in wouldn't give many people any real help (though it would have saved me hunting through the calibre code). Right now, we have to wait until someone with the time, desire and skill to update the driver for this firmware. Tim Legge said he won't have time have time in the next few weeks. Kovid won't (and rightly so) as he doesn't have one of the devices and he has much more important things to do. If I can wrap my head around the code, I might have a look at it. But it won't be too soon.