Change "move data file to" button behaviour

[nick2k3]

Is it possible to change the behaviour of the "Move data file to.." function in Transmission?

Scenario:
I download a very large file on my local hdd.
Then I usually move it to an external hard drive but I would like to keep seeding when the external drive is connected.

Present interface:
- after I've moved the file and deleted the local hdd copy transmission says it cannot find the file;
- I then have to select "Move data file to.." and find the correct path to the file.
- transmission will keep seeding the newly located file

Consideration:
this flow is a bit misleading, many times I simply stopped seeding a large file because I thought "move data file to" might overwrite the old file and start downloading it again.

Suggestion:
if a file is no longer found transmission should ask if I want to "locate file". A simple check ( the very same which is done when the user tries to resume seeding a moved file) might change the text of the button and prompt the user to find the correct path.

It is a very minor improvement but is very simple to implement and may really ease the user experience.

[blacke4dawn]

Just a question, why are you manually moving it and not using that feature to actually move the data?

[nick2k3]

for two reason:
1) I usually download torrents with the external drive disconnected, when I get home I move it to the drive.
2) Sometime, for very large files, moving causes the download to stop and/or Transmission to freeze (I'm talking about quite large torrent ~5/10 GB)

plus, sometime I simply move 10 downloaded file all at the same times...
Well, I COULD just move them using the "Move data file to.." button, but it just seems more obvious to adjust the behavior of the button based on the torrent status.

[blacke4dawn]

To me, it makes more sense to change the "move data" operation to use a separate thread so as to not affect the rest of transmission.