View Single Post
Old 09-17-2010, 09:45 PM   #20
polly
Evangelist
polly ought to be getting tired of karma fortunes by now.polly ought to be getting tired of karma fortunes by now.polly ought to be getting tired of karma fortunes by now.polly ought to be getting tired of karma fortunes by now.polly ought to be getting tired of karma fortunes by now.polly ought to be getting tired of karma fortunes by now.polly ought to be getting tired of karma fortunes by now.polly ought to be getting tired of karma fortunes by now.polly ought to be getting tired of karma fortunes by now.polly ought to be getting tired of karma fortunes by now.polly ought to be getting tired of karma fortunes by now.
 
polly's Avatar
 
Posts: 454
Karma: 270240
Join Date: Aug 2009
Device: Sony PRS 650, PocketBook 360, Astak PocketPro (RIP), Tungsten T3
Quote:
Originally Posted by Starson17 View Post
Taking another tack on an area of the code I know about, is it likely that the leftovers previously were involved in a Merge operation?

I'm thinking of cases where you might be checking books before a Merge: a book might be open in a reader (perhaps to check contents) then the record for that book is Merged into another record - or Windows has the source folder open (perhaps by clicking the Open folder button or using "O"). In both cases, Calibre would be unable to delete the folder and leave it hanging around. DB integrity checks would show nothing and all would appear correct during use, but the leftover folder/files would remain after a library Move.
For what it's worth, not a chance. Some of these hadn't been touched since last November. And in my case, the problem wasn't that some extra stuff got left behind and copied over, but rather that some stuff that was supposed to move didn't.
polly is offline