What steps will reproduce the problem?
1. Have transmission running on linux; using remote-gui on windows;
2. Have path translation setup "properly", in my case:
/Share/Torrents=S:\Torrents
3.
What is the expected output? What do you see instead?
All my torrents are under '/Share/Torrents/Complete' (on my linux server),
which maps (using the "paths" as setup above) to local dir
"S:\Torrents\Complete. Torrents themselves are in a directory underneath
"Complete" that goes by the name of the "torrent file" -- UNLESS, they are
single files (i.e. 1 file in the torrent). For torrents with only 1 file,
it is usually the case that no additional layers of subdirectories are
created.
With the "Paths" mapped properly, all torrent directories and files should
be exactly locatable and be able to be opened on the local system. Right
clicking on a torrent and asking to open directory containing the torrent
should usually open <path>\Complete\<torrentname>\. Individual files in a
torrent will either be under that same directory, or possibly a further
subdirectory down, if the torrent contains subdirectories (example: a
multi-album torrent which places each album into a separate subdir under
the torrent dir).
Instead of opening the torrent directory -- it seems it always (on my
system). Opens the parent dir of the directory containing the torrent
files, or, in my case, directory "Complete". This is true for opening
containing dir's of Torrents as well as files in the torrent.
What version of the product are you using? On what operating system?
Version 1.4 of the gui and 1.9 of transmission.
Running on Win7-64 (transmission is running on SuSE-11.2 x86-64).
Please provide any additional information below.
It is possible someone might argue that 'containing folder', for a torrent,
might be considered the folder containing the torrent folder -- but that's
not usually what the user expects -- they want to see the files that were
in the torrent (which is how utorrent works, for example), the idea, being,
that the 'torrent' are the files listed in the torrent. My torrent doesn't
show the files as being in a subdir -- that's something the torrent clients
do as a convenience, I suspect (maybe it is part of the spec somewhere?).
Anyway -- should open up the dir containing the data for the torrent
(unless, you were to support opening the directory containing the
".torrent" file -- which can (and is, in my situation) be in a different
location entirely.
Thanks for you time...hope this sufficiently describes the issue. I
noticed some similar issues reported, but none reported the details of
their settings.
Original issue reported on code.google.com by astara.a...@gmail.com on 17 May 2010 at 12:55
Original issue reported on code.google.com by
astara.a...@gmail.com
on 17 May 2010 at 12:55