Please look at this my message:
About feature
In short, i want to release feature what is saving changes in renaming files. If i rename file (with KTorrent) the file renames in system but i must seading. Because md5 sum not changed for this file so reading data from this file as possible as before.

It's very difficult i know but important. It's important when i downloading many series from different torrents with different names. But if i want to share a whole series i must rename it for similar names. If i rename its simply my old seading is down. But a people want to download it! Why it must go down if i only rename file? I think it's not correct.

This is already possible in the dialog to select the files to download. Currently the files tab doesn't allow this. We will see for 3.3.

Sorry about this. I can't see it because i see only the text: "Choose a DIRECTORY which you can move the files" if translated from my language to English. And a type of window looks like only change location, not fully rename. Can you change a type of window to view not only folders, to view files too (if i select 1 file and want to rename it). And can you type about finished name (and location if need) in the list of files?
Example:
In torrent at start:

Code: Select all

- myDir
-- fileA
-- fileB
- myDir2
-- fileC
-- fileD

If i rename fileA and fileD, the list can look like"

Code: Select all

- myDir
-- fileA -> renamedA
-- fileB
- myDir2
-- fileC
-- fileD -> renamedD

Then if i change location for fileD(renamedD) and change location and rename fileC:

Code: Select all

- myDir -> ...(... because different path to files into)
-- fileA -> renamedA
-- fileB -> ../../newDir/renamedB
- MyDir2 -> ...
-- fileC
-- fileD -> ../newDir2/newDir3/doubleRenamedD

The path to moved file must shows as relative or absolute (this options needs in settings i think). Then if i move fileC to the same directory which is now located doubleRenamedD (this relative path is "../newDir2/newDir3/") i can see this:

Code: Select all

- myDir -> ...
-- fileA -> renamedA
-- fileB -> ../../newDir/renamedB
- MyDir2 -> ../newDir2/newDir3/
-- fileC
-- fileD -> doubleRenamedD

After the move/rename actions you must look at ecah directories if contain's files located at the same folder. If almost files inside one directory in torrent are located in the same of folder, change path to folder and repair paths to the files. It's very simply and useful for user, i think.

The next problem is this:
Two torrents from two different trackers with different names and different data block size. But it has the same data! If i move it as is and add these torrents to my list i have 2 different not linked downloadings. And i think, have collisions when it downloading the same data blocks! And if they have being had different block size it's very dangerous! Not bad, if you create a "Torrents' block" in this case. I think, it can loks like a folding block (as directory in file list tree) which contains two and more torrents with similar data (not the same). User can merge this torrents. When it mearging, KTorrent must compare each file in first torrent with each file in second. It can compare the size and md5 sum i think, not the name. Then if it find one or more equal files it merging. Then i can merge a third and more files.
This example show you:

1st torrent:
- fileA (size 10, md5: aaa)
- fileB (size 11, md5: bbb)
- fileC (size 12, md5: ccc)

2nd torrent:
- fileD (size 11, md5: ddd)
- fileE (size 11, md5: bbb)

3d torrent:
- fileF (size 11, md5: bbb)
- fileG (size 12, md5: ccc)

After merging 1 and 2 i can see in torrent list:
Merged "1st", "2nd" torrents:
- 1st:
-- fileA
-- fileC
- 2nd:
-- fileD
-- Merged for "1st", "2nd":
--- 1st -> fileB, 2nd -> fileE

After merging "Merged "1st", "2nd" torrents" and 3:
- 1st:
-- fileA
- 2nd:
-- fileD
-- Merged for "1st", "2nd", "3d":
--- 1st -> fileB, 2nd -> fileE, 3d -> fileF
-- Merged for "1st", "3d":
--- 1st -> fileC, 3d -> fileG

It's example for the "Collapse view" of merged torrents. And the next "Each file view" this for the same 3 torrents:

After merging 1 and 2 i can see in torrent list:
- 1st:
-- fileA
-- fileB (2nd -> fileE)
-- fileC
- 2nd:
-- fileD
-- fileE (1st -> fileB)

After merging "Merged "1st", "2nd" torrents" and 3:
- 1st:
-- fileA
-- fileB (2nd -> fileE, 3d -> fileF)
-- fileC (3d -> fileG)
- 2nd:
-- fileD
-- fileE (1st -> fileB)
- 3d:
-- fileF (1st -> fileB, 2nd -> fileE)
-- fileG (1st -> fileC)

So difficult it is loading merged files. You can follow about loading parts with different block size. For example, i think, you split file into the smallest block size and when download a bigger block size you mark several smallest bloack as downloading, i think. But maybe it is must developed in libtorrent not for KTorrent, isn't it?