Opened 12 years ago
Closed 12 years ago
#2001 closed Bug (fixed)
move option for a folder should only move the torrent's file
Reported by: | vlad | Owned by: | livings124 |
---|---|---|---|
Priority: | Normal | Milestone: | 1.80 |
Component: | Mac Client | Version: | 1.52 |
Severity: | Normal | Keywords: | |
Cc: |
Description
when 2 torrents have the same folder name all the files are merged into one folder on download. should one of the torrents move on completion all files within the folder move and the other torrents then fail
everything has to be carefully moved back manually in order for ratio,kindness to be obeyed
on mac OSX
Change History (4)
comment:1 Changed 12 years ago by charles
- Component changed from Transmission to Mac Client
- Owner set to livings124
comment:2 Changed 12 years ago by livings124
- Milestone changed from None Set to 1.80
comment:3 Changed 12 years ago by livings124
- Milestone changed from 1.80 to Sometime
I'm gonna wait on #1483 before implementing, as working around the Mac's move-on-completion code seems pointless if it's going to be ripped out anyway.
comment:4 Changed 12 years ago by livings124
- Milestone changed from Sometime to 1.80
- Resolution set to fixed
- Status changed from new to closed
- Summary changed from duplicate folder names on torrents to move option for a folder should only move the torrent's file
Note: See
TracTickets for help on using
tickets.
I've just tested on "Set Location" feature in the nightly build's gtk client (which uses tr_torrentSetLocation()) to move "torrent a" which shares a folder with "torrent b". it works correctly.
Using the same build and torrents, I've tried the "Delete files and remove torrent" feature (which uses tr_torrentDeleteLocalData()) to move one torrent, but not the other, to the trash. That works correctly too.
Unless the mac client's move-on-complete uses something other than tr_torrentSetLocation(), this should be working properly in 1.70.