jc28735250 Posted January 31, 2008 Report Posted January 31, 2008 Lets say under the downloads panel in preferences,I set the "Put new downloads in:" to be C:\temp,and set "Move completed downloads to:" to be C:\comp,then by setting the Auto load directory to C:\torrent,the program will get torrent files, download them, and move them automatically.Now, the problem is torrents sometimes will have directory names while differing in content.For example, a.torrent and b.torrent may both use the directory "\files".If this is the case, upon completion of one of the torrents,the program will move the folder right away, causing the unfinished torrent to produce a path error.Is there a way to fix this problem?I'm using ver.1.7.7 build 8179
jewelisheaven Posted January 31, 2008 Report Posted January 31, 2008 ... moving only happens when the torrent is complete. Different torrents cannot be used to download to the same file/directory. Seeding can be done as much as you want as many different ways as you want.
jc28735250 Posted January 31, 2008 Author Report Posted January 31, 2008 I don't think you got what I meant.I set it up so when I throw torrent files into a folder, it will automatically download them.But some torrents DO have the same directory by default, and example would be:a.torrent:path:\downloadfiles:\download\test.docb.torrent:path:\downloadfiles:\download\test.aviwhen they are automatically added the directory \download is created and both files go in them.So, using my original examples, it would look something like this:C:\temp\downloads\test.doc.ut!C:\temp\downloads\test.avi.ut!Suppose that a.torrent finishes first and the program proceeds to move the directory.The \downloads directory is moved entirely, along with the unfinished test.avi.ut!:C:\comp\downloads\test.docC:\comp\downloads\test.avi.ut!(C:\temp\downloads is now gone)Now the b torrent will return a path error since C:\temp\downloads doesn't exist anymore.Get my question now?
Greg Hazel Posted February 1, 2008 Report Posted February 1, 2008 Probably does. What should the behaviour here be? The only more reasonable thing I can think of is to move the files one-by-one creating the destination path as needed and removing the old path if empty, instead of moving the root path.Would that be sufficient?
jewelisheaven Posted February 1, 2008 Report Posted February 1, 2008 Is the move operation not the same as the delete operation? From people's requests about deletion taking the whole directory at once, I would have presumed the move operation already works file-by-file.
Greg Hazel Posted February 1, 2008 Report Posted February 1, 2008 Is the move operation not the same as the delete operation? From people's requests about deletion taking the whole directory at once, I would have presumed the move operation already works file-by-file.Correct, delete is per-file, but move is whole directory first.
jewelisheaven Posted February 1, 2008 Report Posted February 1, 2008 In that case, yea I think they should be changed to consistent behaviour. Either as-a-folder, or as individual files.Note to self: I think I've experienced this previously... but I thought it was something on my end. Thanks to jc(lotsofnumbers) for pointing out specifics to reproduce.
Recommended Posts
Archived
This topic is now archived and is closed to further replies.