Custom Query (2449 matches)

As the summary says - currently no UI appears, although there is some code there.

I've attached a patch that provides a full implementation of the UI for the web. It should be on par with the GTK UI functionality.

Also made a small change to a PreferencesWindow.js so plugin settings are saved when the OK button is pressed, not just when the Apply button is pressed.

This is my first time developing with Ext, so it will probably appear a bit warty to seasoned Ext devs :) Feel free to fix it, or point me in the right direction.

The loss of the scheduler plugin (albeit it temporarily) has embolden me to ask for some more functionality in the dBus interface. At the moment, it appears I can pass command arguments, which isn't quite powerful enough for me.

What I'd like to do is be able to stop/start downloading by modifying the max_active_limit configuration through dBus. Basically what scheduler was doing, but something I can call through a program launched by cron. Something like:

bus = dbus.SessionBus()
proxy = bus.get_object('org.deluge_torrent.Deluge', '/org/deluge_torrent/Deluge')
ui = dbus.Interface(proxy, 'org.deluge_torrent.Deluge')
ui.setConfig('max_active_limit', 0)

and

ui.setConfig('max_active_limit', 10)

I'm not quite sure the code above would be the right way to talk to deluge through the dbus ... python is not my language and dbus is something very new to me (about 15 minutes new). If I'm understanding dbus correctly, I might just be able to use dbus_send to pass this information as well.

In any case, the scheduler plugin is a real pain to configure and not quite as flexible as cron would allow me to be. What I'd really like to control is the max_active_limit, but I figure it shouldn't require any more effort to expose the entire configuration, allowing others to do other things ... like between these hours, don't seed, etc.

Also, I noticed IPC is in there too for windows, it might be nice to expose it there as well.

Thanks.

deluge:1.3.0-rc1 libtorrent: 0.14.10.0

Upon transitioning from the scheduler red zone to green, torrents start up again but except for a few which are now in paused mode. How did they get in paused mode?

To be a little more detailed, I think it happens a little like this:

I have 4 torrents, none of which are in paused mode and I am currently in the scheduler's active green zone but I have the queue set to only 2 active like so:

#1 A #2 A #3 Q #4 Q

Upon reaching the red zone the torrents stop but the active ones get assigned a mode of paused so that when the next green zone arrives the lower priority torrents are going instead like so:

#1 P #2 P #3 A #4 A

If it helps to reproduce the bug I am currently starting and stopping deluge client & daemon during each red zone.