Quote:
Originally Posted by kovidgoyal
No, deleting happens after all copying has completed successfully, that way you are never left with a partially mangled library in case of unexpected failures.
The deleting code simply ignores failures, since they are not critical. So yes, something about the original library prevented it from being deleted.
|
Speaking for myself - I would prefer to know via an end of 'task' message that calibre detected failures during the deletion phase. Otherwise I will be left wondering why the old library folder is still there. This is what I happened this morning - my initial 'problem' wasn't all the books as I assumed it was, just a goodly proportion of them -- I didn't run a diff across the two folders
I can't recreate the problem now - Indexing, Malware Detection, Compression, Defragging - they've all changed in Win 10, to some degree at least.
BR