If the scan of the difference can be done in a separated thread, then the commit window can still be responsive, letting us to prepare the commit message (typing the message in the message box) while the other thread compute the diff file list. Changes: status: resolved -Issue 161: Commit window too long to appear Steve Borho / sborho on Wed, 0200: Comment: I'm really surprised it's freezing at startup.In 0.8 all it does when you open the commit tool is run repo.status() and then get the diffs for just the first file.* Fix issue when adding torrents without a 'session'.
* Fix bugs with unicode torrents in Auto Add plugin.
Mixing pygtk & qt might leave a bad taste in some people's mouth. You are receiving this either because you are the owner of the issue, or you are following the issue.
Issue 161: Commit window too long to appear Steve Borho / sborho on Fri, 0200: Comment: See the discussion on issue #122, especially the last comment. The default mode for the commit tool must be much more efficient than the way it works in 0.7.n, for both performance and robustness reasons.
fixes #1343 * Fix key error after enabling a plugin that introduces a new status key * Ignore global stop ratio related settings in logic, so per torrent ones are used.
* Ensure preferencesmanager only changes intended libtorrent session settings.