Opened 10 years ago

Last modified 10 years ago

#3684 assigned Bug

Incomplete torrents location mismatch

Reported by: starmoon Owned by: charles
Priority: Normal Milestone: Sometime
Component: Daemon Version: 2.11
Severity: Normal Keywords:
Cc:

Description

Incomplete torrents shows the file location in "download-dir", but accurally it's in "incomplete-dir".

When use transmission-remote-gui to "open file in network share". It shows file not found.

Change History (8)

comment:1 Changed 10 years ago by charles

I don't really understand this ticket. Could you rephrase this suggestion?

comment:2 Changed 10 years ago by starmoon

set incomplete-dir-enabled to true, and set incomplete-dir to somewhere else than download-dir.

Unfinished torrent's property shows the location is where the download-dir was. But actually the torrents data is resident in incomplete-dir.

This bug does not matter with download or seeding. but will confuse when you want to open torrent's directory to check some partical finished file out. (e.g. right click the torrent and select "open in network share" with transmission-remote-dotnet)

comment:3 Changed 10 years ago by charles

  • Milestone changed from None Set to Sometime
  • Owner set to charles
  • Status changed from new to assigned

we should probably make torrent.c's "current-dir" property visible to RPC clients.

comment:4 Changed 10 years ago by charles

starmoon, I'm thinking about adding "current-dir" as an argument for torrent-get. In torrent.h this field is documented this way:

    /* Where the files are now.
     * This pointer will be equal to downloadDir or incompleteDir */
    const char * currentDir;

starmoon, do you think this would solve the problem? Am I understanding the problem correctly?

2.13 will probably come out in the next couple of days. If the above sounds good to you, let me know and I'll put this into 2.13.

comment:5 Changed 10 years ago by charles

  • Summary changed from Imcomplete torrents location mismatch to Incomplete torrents location mismatch

comment:6 Changed 10 years ago by jordan

starmoon: would adding current-dir to torrent-get in RPC solve this ticket?

comment:7 Changed 10 years ago by jordan

starmoon: ping

comment:8 Changed 10 years ago by reardon

I'll jump in and say that, yes, it will be useful to have a current-dir in RPC. I will provide a transgui patch (the fpc remote, not the dotnet remote) should this occur.

Note: See TracTickets for help on using tickets.