|
Actually, the thing I *really* don't understand is how this is causing a Calibre problem.
Even if there was some sort of conflict, Dropbox would have absolutely no reason to have a random file locked *before* it was changed.
So what must be happening is that Calibre writes to the file, *pauses*, and then tries to write again but see that Dropbox has the file open for reading. I...can't figure out why Calibre would be doing that on a metadata change.
|