Move on to next queue item when downloaded
Status: Beta
Brought to you by:
d0c54v4g3
Menu
▾
▴
#24 Move on to next queue item when downloaded
Right now, if the program is set to keep sharing until
I hit a ratio of 1:1 for instance, it'll only start
downloading the next queue item once the first one hits
1:1.
This is troublesome on small torrents, since it can
sometimes take days to hit 1:1 and this time could be
spent downloading (and seeding) other things. The
alternative is to babysit the queue, which can be
troublesome when you want to download half a dozen
things as fast as possible.
There should be an option to make Rufus move on to the
next queue item after a successful download, which
would leave the previous torrent to seed while the next
one would download. ABC has an option to do this, so it
seems like a logical feature.
Logged In: YES
user_id=844378
The problem of how to control queueing to meet different scenarios while being easily user-controllable seems hard to me. In my case I typically have some almost entirely idle torrents on strict ratioed trackers, and then some files I want to seed heavily which I've recently downloaded, and one I'm downloading. Of the latter 3 I probably want to limit this to three max, blocking downloads until they've hit their seed-after-completion rules. But then I have additional torrents I want to "not count"
Azureus basically disqualifies "forced" torrents from the max counts, which is useful but confusing.
I think for most scenarios a "total torrents limit" number combined with a "downloading torrents limit" number would be reasonable. That is, if the number of active torrents meets or exceeds "total torrents limit", no queued torrents will be activated, while if the number of active incomplete torrents meets or exceeds the "downloading torrents limit" no queued incomplete torrents will be activated, although queued torrents which are seeds might activate.
I _think_ this is pretty comprehensible to most users, and gives relatively easy to understand behavior. You can have unlimited seeding by setting the total limit to 0 or -1 or None, and you can have unlimited downloading by setting the downloading torrents limit to similar. Default config would be something like downloading 1, total 4.
I encourage you to do independent research on queueing control UI. There might be much cleverer things you could do.
Additionally, I'd be happy to implement some different scenarios, but don't know, and am not really interested (sorry) in learning to program wx. If you can just give me a form with some variables to play with I can send you patches with my comments on usability experience. Yeah I could hack it into a configfile but i don't think that will provide a good testbed for clarity. (jrodman at rufus.spamportal.net)