Quote:
Originally Posted by dwanthny
So you did a drag-n-drop from the calibre library folder to the available formats window in the edit metadata area. This is essentially a "move" and after a file is successfully copied/moved to the new location (same location in your example) the original would be deleted. This causes a 0.0 byte file.
|
Yes, but the whole story is:
- I erased the specific file format from Calibre (namely PDF here)
- I did a drag-n-drop in the same position of the old file
- I added a new file format for this entry, that by chance is a file in the same position and w. the same name
Quote:
Originally Posted by dwanthny
You can't do this via two different file managers in Windows because it recognizes they are the same and throws up a error box and an annoying sound to let you know this isn't right.
It seems calibre (python) isn't so forgiving. I tried this myself and did end up with a 0.0 byte file that was garbage.
|
It's right, but I was assuming that once the file format was erased from Calibre DB it should release the manage of this specific file. It turned out to be wrong...
Quote:
Originally Posted by dwanthny
Read here to find out how to create a ticket. But like the old joke, Patient: Doctor, Doctor it hurts when I do this.... Doctor: Well don't do that.
|
But I like to do that!
Quote:
Originally Posted by dwanthny
Congrats on being unique enough to find this "Opening of destruction".
|
Thanks
Quote:
Originally Posted by kovidgoyal
Should be fixed in next release. calibre will now simply ignore attempts to overwrite a file with itself.
|
Great!And that means that I don't need to annoy you with a new bug ticket!
Bye!
--
"The Answer to the Great Question …"
"Of Life, the Universe and Everything ..." said Deep Thought.
"Is ... " said Deep Thought, and paused.
"Forty-two," said Deep Thought, with infinite majesty and calm.