jdhore wrote:
6. This was removed. Again, according to the devs, it's not worth the overhead so it was removed. I personally think it should be added back, but they said "Never", so meh...I'll stop bitching.
No!!!! Why was it removed? It was a great feature! Now how am I suppoused to see how much time left do I have to seed?
i was messing around with the configurations, and noticed that the "max new connections per second" and "max half connections" were missing. This feature was useful since i also use emule and have to divide my half connections and new connections between the two. Will it be implimented in the finalized version?
jdhore wrote:
6. This was removed. Again, according to the devs, it's not worth the overhead so it was removed. I personally think it should be added back, but they said "Never", so meh...I'll stop bitching.
No!!!! Why was it removed? It was a great feature! Now how am I supposed to see how much time left do I have to seed?
PLEASE put the peers % of completion back!!!
umm...you really need to:
1. Not type like a 7-year old on AIM.
2. Learn to read. I mentioned why it was removed in my original post. As i said, it was because the devs don't care for it and it was too much bandwidth overhead so it was removed. As for it coming back...That's unlikely...I've asked both devs multiple times and made several examples for my reasoning and they said no. My suggestion is that you either stick with Deluge 0.5.x or just give it up.
jdhore wrote:
6. This was removed. Again, according to the devs, it's not worth the overhead so it was removed. I personally think it should be added back, but they said "Never", so meh...I'll stop bitching.
No!!!! Why was it removed? It was a great feature! Now how am I supposed to see how much time left do I have to seed?
PLEASE put the peers % of completion back!!!
umm...you really need to:
1. Not type like a 7-year old on AIM.
2. Learn to read. I mentioned why it was removed in my original post. As i said, it was because the devs don't care for it and it was too much bandwidth overhead so it was removed. As for it coming back...That's unlikely...I've asked both devs multiple times and made several examples for my reasoning and they said no. My suggestion is that you either stick with Deluge 0.5.x or just give it up.
Just because it won't exist natively doesn't mean it won't exist.
If you really want that feature write a plugin to do it.
I've gone back to the last stable release of the client, at least for the time being as I could not handle the inherent performance lag with the release candidates and the lack of a working blocklist importer, although I hope these issues will be rectified in subsquent releases as I love this client and its new look, will keep a lookout for further releases and news.
devil81 wrote:I've gone back to the last stable release of the client, at least for the time being as I could not handle the inherent performance lag with the release candidates and the lack of a working blocklist importer, although I hope these issues will be rectified in subsquent releases as I love this client and its new look, will keep a lookout for further releases and news.
A new blocklist plugin (that works and has some new features) should be in 1.0 RC3 which should be coming out either today or tomorrow. Also, we're working on the performance issue.
I really don't like the 'small icons, no text' option set for the toolbar by default, and the fact that isn't adjustable from the interface preferences is even worse. It feels very "limiting", doesn't obey my System - Preferences - Appearances default option, and I'm not able to adjust it.
Also, several times now I had the deluge process decide to use 100% of one of my cpu's. I had to close and reopen deluge. Is there any info I can check next time and provide?
Vadi wrote:I really don't like the 'small icons, no text' option set for the toolbar by default, and the fact that isn't adjustable from the interface preferences is even worse. It feels very "limiting", doesn't obey my System - Preferences - Appearances default option, and I'm not able to adjust it.
Also, several times now I had the deluge process decide to use 100% of one of my cpu's. I had to close and reopen deluge. Is there any info I can check next time and provide?
This is a known issue and we're trying to identify the cause.
$ python setup.py build
running bdist_egg
running egg_info
writing Label.egg-info/PKG-INFO
writing top-level names to Label.egg-info/top_level.txt
writing dependency_links to Label.egg-info/dependency_links.txt
writing entry points to Label.egg-info/entry_points.txt
Traceback (most recent call last):
File "setup.py", line 59, in <module>
"""
File "/usr/lib/python2.5/distutils/core.py", line 151, in setup
dist.run_commands()
File "/usr/lib/python2.5/distutils/dist.py", line 974, in run_commands
self.run_command(cmd)
File "/usr/lib/python2.5/distutils/dist.py", line 994, in run_command
cmd_obj.run()
File "/usr/lib/python2.5/site-packages/setuptools-0.6c8-py2.5.egg/setuptools/command/bdist_egg.py", line 167, in run
File "/usr/lib/python2.5/distutils/cmd.py", line 333, in run_command
self.distribution.run_command(command)
File "/usr/lib/python2.5/distutils/dist.py", line 994, in run_command
cmd_obj.run()
File "/usr/lib/python2.5/site-packages/setuptools-0.6c8-py2.5.egg/setuptools/command/egg_info.py", line 171, in run
File "/usr/lib/python2.5/site-packages/setuptools-0.6c8-py2.5.egg/setuptools/command/egg_info.py", line 252, in find_sources
File "/usr/lib/python2.5/site-packages/setuptools-0.6c8-py2.5.egg/setuptools/command/egg_info.py", line 306, in run
File "/usr/lib/python2.5/site-packages/setuptools-0.6c8-py2.5.egg/setuptools/command/egg_info.py", line 333, in add_defaults
File "/usr/lib/python2.5/site-packages/setuptools-0.6c8-py2.5.egg/setuptools/command/sdist.py", line 45, in walk_revctrl
File "/usr/lib/python2.5/site-packages/setuptools-0.6c8-py2.5.egg/setuptools/command/sdist.py", line 52, in _default_revctrl
File "/usr/lib/python2.5/site-packages/setuptools-0.6c8-py2.5.egg/setuptools/command/sdist.py", line 98, in entries_finder
NameError: global name 'log' is not defined