Custom Query (2447 matches)


Show under each result:

Results (319 - 321 of 2447)

Ticket Resolution Summary Owner Reporter
#635 Fixed Autofocus to password input in webui... mvoncken

Currently, whenever the user goes initially goes to the login page on the web UI, they have to manually change the focus to the password input box (by clicking on the input box or tabbing through the links). Attached, you will find a diff (against the -current version of deluge) to change the focus to the password input box on window load. You will notice from the diff that I have coded the event within a script element on the login page. I looked through the mootools stuff and site, but it appears that the 'addEvents' method is only included with the mootools event package. Since, I didn't see that this mootools package was included with deluge, I therefore hand-coded the focus for the password input box on window load. If you have a better suggestion on how to implement this, I would be glad to hear and implement it.

BTW, you will note that the diff also includes changes to the login failure error message. This is due to the fact that there is a space missing between the comma and the 'try' word. I would also recommend that the error CSS class declaration (in template_style.css) be expanded beyond 200 pixels. The error phrase, "Password is invalid, try again.", is longer than the error class' tiny 200 pixel length.

#636 Fixed start_localhost deluged config to gtkui location... andar anonymous

While trying to hack on deluge (installed in a develop dir) and preserve my current deluge configuration, I noticed that deluged would use the configuration from my current deluge configuration. As I didn't want to risk messing up my current config or torrents, I looked around the deluge and found that, when deluge is started in classic_mode, the daemon is started and the config location is the default one (even if a gtkui config location is specified). Therefore, the attached diff feeds the gtkui config location to the daemon if the daemon is started up in classic_mode. You will notice that the start_localhost method in connectionmanager uses: 1) the long options, and 2) the winprocess call isn't changed. The first because the short options weren't being correctly parsed in main (or my poor usage of python is so bad that I could only get the long options to work). The second was because I don't have a windows box to test changes to the winprocess call on.

The connectionmanager file diff also includes usage of the DEFAULT_CONFIG host if: (1) the host isn't specified, or (2) the port was hardcoded. The reason is that I hate to see strings hardcoded into code, and the DEFAULT_CONFIG is specified -- therefore, it should be used. I also think that the logic for the 'classic_mode' and 'autoconnect' (along with 'autoconnect_host_uri' and 'autostart_localhost') could lead to configuration problems for the users, but I'll have to look at the whole thing more in depth in order to see if the logic should be reworked.

BTW, I also had to hack the filtertree and tracker_icons files so that they didn't, as well, write to the default config location if that location wasn't specified at deluge startup.

#637 Fixed Progress bar for "move storage" andar

A progress bar to give the user feed back on moving the storage of a torrent from one partition or disk to another.

Batch Modify
Note: See TracBatchModify for help on using batch modify.
Note: See TracQuery for help on using queries.