loki wrote:My report for Vista x64...
1. We get a msi file now, exciting, but the file seems excessively big and when it installs everything it says it takes up 216Mb... that is not very cool.
2. Control panel icon is blank.
3. Scrolling through a list of files in the torrent list has like a lag or unresponsiveness, the whole program in general but it is most noticeable/annoying here.
4. Seems as though clicking a torrent file or dragging and dropping a torrent file into the window doesn't add to Deluge, has to go through the add torrent button and select it that way.
5. Torrents in the seeding list rearrange themselves when restarting, won't move with the arrows (queuing?).
6. What does the organize or test plugin do?
7. I added a torrent to seed, it checked through to make sure it was all there and started seeding all fine, I looked into the files tab, definitely digging the new folder layout rather than just the list of files, but I noticed it shows Priority - Do not download I tried changing it, doesn't change, and one file shows 5 billion whatever % done... picture attached to see.
1. It installs all the necessary dependencies that are generally not available on windows machines. We will have an installer without the dependencies bundled for upgrading a currently installed deluge. We might be able to further trim the dependencies in the future, but it's always a chore working with windows.
2. Control panel icon?
3. This might be resolved with the fix to the files tab percentages I committed.
4. Drag n' drop did not make it into this version. Please file a feature enhancement ticket and set the milestone to 1.1.0 please.
5. Seeding torrents do not have queue positions, but rather seed ranks based on the seed settings you have chosen. Here is a quote from the libtorrent docs concerning queueing:
queuing
libtorrent supports queuing. Which means it makes sure that a limited number of torrents are being downloaded at any given time, and once a torrent is completely downloaded, the next in line is started.
Torrents that are auto managed are subject to the queuing and the active torrents limits. To make a torrent auto managed, set auto_managed to true when adding the torrent (see add_torrent()).
The limits of the number of downloading and seeding torrents are controlled via active_downloads, active_seeds and active_limit in session_settings. These limits takes non auto managed torrents into account as well. If there are more non-auto managed torrents being downloaded than the active_downloads setting, any auto managed torrents will be queued until torrents are removed so that the number drops below the limit.
The default values are 8 active downloads and 5 active seeds.
At a regular interval, torrents are checked if there needs to be any re-ordering of which torrents are active and which are queued. This interval can be controlled via auto_manage_interval in session_settings. It defaults to every 30 seconds.
For queuing to work, resume data needs to be saved and restored for all torrents. See save_resume_data().
downloading
Torrents that are currently being downloaded or incomplete (with bytes still to download) are queued. The torrents in the front of the queue are started to be actively downloaded and the rest are ordered with regards to their queue position. Any newly added torrent is placed at the end of the queue. Once a torrent is removed or turns into a seed, its queue position is -1 and all torrents that used to be after it in the queue, decreases their position in order to fill the gap.
The queue positions are always in a sequence without any gaps.
Lower queue position means closer to the front of the queue, and will be started sooner than torrents with higher queue positions.
To query a torrent for its position in the queue, or change its position, see: queue_position() queue_position_up() queue_position_down() queue_position_top() queue_position_bottom().
seeding
Auto managed seeding torrents are rotated, so that all of them are allocated a fair amount of seeding. Torrents with fewer completed seed cycles are prioritized for seeding. A seed cycle is completed when a torrent meets either the share ratio limit (uploaded bytes / downloaded bytes), the share time ratio (time seeding / time downloaing) or seed time limit (time seeded).
The relevant settings to control these limits are share_ratio_limit, seed_time_ratio_limit and seed_time_limit in session_settings.
6. Nothing at the moment. The test plugin was simply a way to do some testing on the plugin system and the Organize plugin was something mvoncken was working on, but it has no functionality.
7. The file progress api changed a bit in a last minute libtorrent sync, so it went unnoticed. I have just fixed this in svn and it will be fixed in the next RC.
Thanks for the feedback!
Deluge
