-
-
Notifications
You must be signed in to change notification settings - Fork 3.8k
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"Temporary Folder" feature redesign #7164
Comments
@sledgehammer999, @qbittorrent/frequent-contributors, let's discuss it! |
I would suggest a default cache folder behaviour where
an argument could be made to make all of the above optional (i.e. add settings items for them). I've also read some suggestions where people ask that they can set save paths for individual files. For that use-case a per file/folder based override could be implemented that either saves directly or moves from cache depending on if the cache folder is enabled. File tracking & force-rechecking for torrents would have the application check both paths for each file. In case of it existing in both places a prompt could be shown or an automated (saved) action could be performed (i.e. keep newest, keep biggest, keep oldest, etc.). If this can get implemented in such a way that folders and files are not differentiated from each other this should also work for torrents without a root folder. |
I agreee |
I'm not sure I understand what you mean... Option to reset the default value from settings during torrent addition (ie. I set "Use temp folder" in settings but I can disable it for some torrents in "Add torrent" dialog)? |
And yet... a little to limit your imagination, I will say that we technically can't recheck some particular file, but the entire torrent only. |
More precisely a right click option, like download in sequential order, but your idea is not bad either.
Ah, yes sorry, that was my bad, torrents use hash crc. But this will go back us to my first problem. |
This looks like a suitable option. But it has one logical problem. Let's say I add multifiles torrent and I uncheck some files. Then it plays like you suggest: |
Hm, good question. It's a rare case wich needed check the temp folder and recheck options both and a partial completed torrent to. Basically this option is decide to remove the don't use temp folder option for a partial torrent. Then the torrent is go to download state. |
I don't see a fundamental difference in the relation to disk I/O. |
In my experience, copy many small files slow down HDD I/O, probably the creation of hundreds of new entries in the FAT table. But it's FAT32/NTFS, I dont work under linux/mac. But yes, no need to overthinking it, if it's to slow that way, the user can simply switch off. |
I found a simple solution to the problem. I abandoned qBittorrent and adopted Deluge. With Deluge my folder stays nice and clean. I loved qBittorrent and would come back if it cleaned up after itself, reliably. |
Joke's on you. In the last week 3 patches were merged. One fixing the bug about not removing the temporary folders, and the others using the torrents' original names instead of the "IDs". @glassez is this thread still valid? |
Yeah but I can hardly blame ThePOO -- this folder nonsense was ignored for far too long by qBittorrent. |
Please do not claim your opinion as the only true.
Yes. I'd like to hear more opinions about the following:
Currently we have Torrent-based temporary folder feature. IMO, it has some drawbacks. I'm thinking to change it to File-based feature. Later I will present here an example algorithm how it could work. |
You want to move individual files to their final destination? |
Thanks. I will be re-loading qBittorrent and testing shortly.
Thanks, again.
…On 8/5/2017 12:27 PM, sledgehammer999 wrote:
I found a simple solution to the problem. I abandoned qBittorrent
and adopted Deluge. With Deluge my folder stays nice and clean. I
loved qBittorrent and would come back if it cleaned up after
itself, reliably.
Jokes on you. In the last week 3 patches were merged. One fixing the
bug about not removing the temporary folders, and the others using the
torrents' original names instead of the "IDs".
@glassez <https://github.com/glassez> is this thread still valid?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#7164 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AJV4peYlaFPLVVBD7MfMvalWwDGRza8sks5sVMIGgaJpZM4OiQh2>.
--
|
The patch fixing the bug where the folders weren't removed is in 3.3.15. The others aren't included yet in a release. |
Great! A bunch of my friends will be happy to hear it's fixed and
will be waiting on my testing --- they are chomping at the bit to get
back into qBitorrent. Thank you for all your efforts to support
qBittorrent --- YAY!!!
…On 8/5/2017 3:37 PM, sledgehammer999 wrote:
Thanks. I will be re-loading qBittorrent and testing shortly.
The patch fixing the bug where the folders weren't removed is in
3.3.15. The others aren't included yet in a release.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#7164 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AJV4pfDsdWrICztC9HTbSV0LFsjuFDAJks5sVO7CgaJpZM4OiQh2>.
|
Yes. Unless there are some strong objections. |
I'm not sure I'm in favor or object to that, particularly because I've never used a torrent client with that feature. But one thing I can think of is it might get annoying to see incomplete torrents popping up in my "Completed" folder, and then have to go check qBT to see if it has actually finished or if all it did was download the read.me file. If I want to sample the finished parts of a collection or series, I would be perfectly capable of doing that if it weren't for the slew of randomly named folders in my "Downloading" folder making it a hassle. |
I'm not going to change it until I get approval here. |
Can we add an option to use unique subfolders as in 3.3.x? |
The more I delve into it (I have been thinking about this for quite some time), the more I'm leaning towards the idea that the best solution is to be rid of the "Temporary folder" approach.
@sledgehammer999, what do you think about? |
Now that sounds much more sensible—something I might actually use. I currently do exactly what you describe with my torrents—through externally moving their files, then resetting the affected torrent for that new location. Having qBittorrent do the same thing in a way that is not so annoying—that I can get behind. |
@glassez, @sledgehammer999: One thing, however, is that it might be nice to see a per-torrent option for this. At the initial torrent options menu, you would then have the "Download to" drop-down box. Beneath that a "Move files when complete" check-box—which enables a "Move to" drop-down box. Then each torrent could be moved to a different completed folder. What do you think? |
@LordNyriox, when I say
I mean this behavior as well (since we have this behavior for regular/complited save folder). |
Also we can solve "semi-downloaded torrent" issue by introducing appropriate option (however, I can't think of its name). I mean, should we consider as completed only fully downloaded torrents or torrents that have completed downloading of all selected files. |
EDIT: * facepalm *
I believe that is ultimately dependent on whether qBittorrent is expected to continue downloading un-selected files after all selected files have been fully downloaded. There is also a corner case of what happens if someone selects an un-selected file after the torrent is already completed. Avoiding potential glitches like that, is why I generally avoid letting qBittorrent automate my post-downloading actions. |
Current behavior is when torrent finishes downloading of all selected files it become complete, but if you select an un-selected file after the torrent is already completed it become incomplete again.
Use cases:
|
+1
EDIT: * facepalm * |
Yes. This is a consequence of my previous answer:
User can override default "regular" save folder in Add New Torrent Dialog so he will be able to override "incomplete" folder as well using discussed feature. |
@glassez I agree that it would be far simpler code-wise and probably logic-wise(from user POV) to have "move to folder after completion" functionality. As for what we should do when user selects another file while the torrent is already completed and moved: Having it as an option is an approach but it sounds a bit bloaty. Does anyone know what uTorrent does? (pretty much everyone here takes utorrent as de facto standard) |
If I remember correctly, utorrent just start download the missing files in the current location. So if a partially selected torrent downloaded and moved the "complete folder" it's start download there, if select an incomplete torrent, then it's just add the files, and download there, and the whole torrent move the "complete folder", when the download finised. |
I could be wrong but here is my take: From a user POV the "move-after-completion" is a one time event, a command. I don't think he expects his files to be moved back when he selects another one for download. And from a code point of view it is simpler to implement. After we do the move, we no longer need to remember the previous location. Especially if it is a per-torrent setting. |
Yes. As I previously mentioned, typically, the user knows what he wants from this torrent so typical u cases are:
(Exceptional case) User selects some files to download and he isn't sure he needed or not the remaining files (or he just changed his mind and decided to download any files once the torrent has already been moved to the "completed" folder. I don't think he expects his files to be moved back. Otherwise he can manage save folder for this torrent manually. |
In fact, this feature is limited to setting the "moving" trigger to be activated once torrent finished downloading (either all or just selected files depending on user choice).
Yes. This will give us a simple, reliable and maintainable code. |
@sledgehammer999, as I understand it, you approve "move-after-completion" feature? |
Might I suggest adding to the "move-after-completion" the option to have this work for individual files within a torrent as well? Could be done by moving the file & then setting the priority to "do not download" or, with a little more work, adding a special status to mark it as moved so that when the entire torrent is finished qBT knows that it can rediscover it in the moved-to folder. |
You mean not seeding completed files until the entire torrent is complete? How do you see the sense in that? You just want not to waste the place in "incomplete" folder (e.g. on limited size disk)? |
I think so(about complexity). |
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
The problem is that everyone sees (or wants) in this feature something different, and the behavior, which does not fit into his vision, he feels wrong. There are some issues with this feature (e.g. #5503, #7113, #7137). Each offers to fix it on his manner, without thinking about its overall logic. Lately I often think about how to change it. I propose to discuss "desired" implementation of "Temporary folder" feature in this topic.
You can speak here how you can see this feature. I want a detailed description, possibly with some sort of algorithms of its activity in some circumstances.
The main problems that should be addressed are:
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
The text was updated successfully, but these errors were encountered: