Bitcomet 1.06 seems to have qute a few changes from previous versions.
Functionality has been reduced in at least one area that I have come across. If you want to manually move your downloads to another partition or drive, you will have quite a few problems in this release.
In previous releases, you could stop the task or stop Bitcomet completely, then manually move the files from one drive or partition to another, restart, then change the destination property of the task, and either manually hashcheck or the program would detect a change and ask if you wanted to hashcheck.
Now, if you move files, when the task or Bitcomet are not running, you cannot just change the destination property and continue. You will get a popup showing that the destination already exists, without presenting the option of hashchecking the new destination. It just makes you stop.
The only work-around is to delete the task, but be sure to uncheck the box for deleting it from the torrent collection, then go to the torrent collection window and restart the torrent. (You can just double-left-click the mouse on the selected torrent.) You will be informed that the task has been deleted and be given the option to re-download the torrent. (It doesn't really redownload the torrent, but just reloads it from the torrent archive on the root/system drive.) Bitcomet then presents you with the hashcheck/continue option.
Again, the programmers have taken the easy way out, by only presenting the pop-up telling you it can't move the files, because they already exist. Have these guys completely forgotten everything they learned about "Useability" in college?
As far as I am concerned, the "Move" feature is broken completely. Have you tried to move files within Bitcomet lateley? I believe they no longer pass the move off to the native environment "move file" function. They are trying to do it within Bitcomet itself, with disastrous results. It can take HOURS to move a few files. More likely than not, it will fail, saying that it cannot access the file because it is being used by another process, which is probably a Bitcomet process.
Since the move function is broken in two ways, your only option is the around-your-thumb sequence of moving the files outside of Bitcomet, then deleting and "re-downloading" the torrent task.
Come on guys, what part of "if it's not broken, don't fix it" do you not understand? Don't take the old AT&T developer stance that "it's not a flaw, it's an undocumented feature!".
Shadow
