Explicit specification of destination directory

[GoogleCodeExporter]

If we initiate the command 'Add torrent with options' and then choose an
available torrent file, we rather typically get a form, similar to the one
shown at the attached picture.

It is clear from the picture that when the torrent was been created by its
seeder, the listed files were located in a folder named 'import export2'.

But let us suppose for a moment that in the correspondence with my personal
standards I'd like to download these files in a folder named
'Import-Export/VIDEO_TS' and then to seed them from this folder.

However, if I specify the path '/share/Video/Import-Export/VIDEO_TS' in the
field 'Alternate destination directory', after the start of the torrent the
files will be downloaded in the folder
'/share/Video/Import-Export/VIDEO_TS/import export2' rather than to the
desired folder. This means that your client (unlike, for example, uTorrent)
append the original folder name to the specified path BY DEFAULT.
Meanwhile, I think it would be very convenient (at least for some
capricious users ;-) ), if this can be made only OPTIONALLY, for example,
by a checkbox 'Append original folder name'.

Is this enhancement too difficult?

Original issue reported on code.google.com by kostia.i...@gmail.com on 21 Jan 2010 at 7:51

Attachments:

• DestinationDirectory.png

[GoogleCodeExporter]

I second that, it is usefull feature :)

Original comment by ml.ci...@gmail.com on 21 Jan 2010 at 10:42

[GoogleCodeExporter]

I think, T add automatic the torrent name to files. I cant find notting in rpc-
spec.txt, how can i change this :(

Original comment by elso.and...@gmail.com on 21 Jan 2010 at 11:00

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Again, this feature is supported by http://www.utorrent.com/.  However, 
Transmission
does not support it currently (see http://trac.transmissionbt.com/ticket/1220). 
:-(

Original comment by kostia.i...@gmail.com on 22 Jan 2010 at 8:13

[GoogleCodeExporter]

Yes, I think Transmission server doesn't have this very useful feature yet. So, 
it's 
not a transmission-remote-dotnet fault, but Transmission itself. I hope, the 
author 
of T will add this feature some day.

Original comment by alexey.m...@gmail.com on 22 Jan 2010 at 8:14

[GoogleCodeExporter]

I mark this issues as accepted, and when Transmission implement the necessary 
function, we can make this.

Original comment by elso.and...@gmail.com on 22 Jan 2010 at 11:54

• Changed state: Accepted
• Added labels: Priority-Low, Type-Enhancement
• Removed labels: Priority-Medium, Type-Defect

[GoogleCodeExporter]

Original comment by elso.and...@gmail.com on 23 Jan 2010 at 10:42

• Added labels: Milestone-Sometime