Quote:
Originally Posted by jackie_w
ETA: Mea maxima culpa. I really need to remember that when alpha/beta-testing I must revert to using the official SmartDevice App Interface 0.0.1 driver, not the subclassed personal one I've been using for ages to force a small CSS change during book transfer. I've redone the Content Server tests (long-press and short-press) for 2 not-on-device-books. Filenaming is working correctly in 5.0.0.4 for the 'Use calibre's file names' setting.
I realise it is not reasonable for me to pursue why my personalised driver fails to rename correctly at this time. Maybe later (much later) when you have some free time after the v5 production release.
|
Sorry, I didn't notice this edit.
Depending on when you subclassed the driver and depending on what methods you overloaded, you might be missing some of the CC/calibre "feature negotiation". The two programs converse about what each is capable of doing and pick the common subset.
In particular I suspect that the canSupportLpathChanges options introduced somewhere around calibre 2.30 might be missing in your version, especially if you overloaded _put_file.