Improper Torrent Loading (Duplication of Files)

[eepman]

As of 1.3.5 deluge makes a copy of every torrent in the state folder under AppData? when it is loaded. I don't believe this is efficient when the option to store torrents in a separate directory is turned on.

Another issue I have noticed is that if you are loading a torrent from the same directory as the directory set to copy your .torrent files to it will replace the existing file instead of realizing that the file is already in the right place.

Running deluge version 1.3.5 with libtorrent 0.16.1 on win32

[gazpachoking]

As for the first bit, deluge needs the copy of the torrent when restarting the daemon. I don't think it's good to have the only copy out in the user's copy to directory. What happens when the user deletes or renames it? I don't think they would expect that deluge couldn't resume the file.

As for second issue, I don't really think it's necessary or worth it to check if the destination is already identical, there wouldn't really be much gain from that.