Custom Query (2449 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (169 - 171 of 2449)

Ticket Resolution Summary Owner Reporter
#452 Fixed arch pkgbuild fix sadrul anonymous
Description

The PKGBUILD included in the download section has a small error:

  • install -D -m644 pixmaps/deluge.svg $startdir/pkg/usr/share/pixmaps/deluge.svg

+ install -D -m644 deluge/data/pixmaps/deluge.svg $startdir/pkg/usr/share/pixmaps/deluge.svg

#41 Fixed A redesign for the "remove torrent" modal dialog window is needed andar anonymous
Description

The "remove torrent" modal dialog window is a good example for really bad design. It doesn't conform to GNOME Human Interface Guidelines. But screw that, they're just guidelines, right? No. Get a UI designer on your team. This isn't meant as an attack. I'm giving you valuable insight here. Deluge is a good application overall.

Currently this is what it looks like:


Text (not sure, translating on the fly, using Polish version): Do you really want to remove the torrent/torrents?

Tickboxes:

  • Delete files
  • Delete .torrent files

Buttons:

Yes, No.


How should it look like?


Text: Remove %n torrent(s)? (Please enable proper plural forms support, this (s) is just a sad hack)

Buttons:

Remove from list only

Remove and delete .torrent files

Remove and delete downloaded files

Remove and delete all associated files


If you think the labels on buttons will be too long, don't worry, they won't be. It's all about usability, readability, interface standardization (I was really stumped by this dialog and didn't know what to do at first) and not trying to mimmick a clumsy Windows-like interface. Avoid modal dialogs like the plague, but if you really need them (like here), again, avoid "Yes" and "No" button labels at all costs. I dare you show me one GNOME application in svn.gnome.org having such labels on any button. That would be a sign of downright bad design.

Look at this bug to see a mockup of what am I on about here https://bugs.launchpad.net/mintinstall/+bug/174548

I hope you consider this proposal for a future version.

#3278 Fixed argparserbase: exception when creating the pid file DjLegolas
Description

a user reported about a TypeError:

Jun 22 21:00:22 htpc deluged[21885]: Traceback (most recent call last):
Jun 22 21:00:22 htpc deluged[21885]:   File "/usr/bin/deluged", line 11, in <module>
Jun 22 21:00:22 htpc deluged[21885]:     load_entry_point('deluge==2.0.3', 'console_scripts', 'deluged')()
Jun 22 21:00:22 htpc deluged[21885]:   File "/usr/lib/python3.7/site-packages/deluge/core/daemon_entry.py", line 87, in start_daemon
Jun 22 21:00:22 htpc deluged[21885]:     options = parser.parse_args()
Jun 22 21:00:22 htpc deluged[21885]:   File "/usr/lib/python3.7/site-packages/deluge/argparserbase.py", line 250, in parse_args
Jun 22 21:00:22 htpc deluged[21885]:     return self._handle_ui_options(options)
Jun 22 21:00:22 htpc deluged[21885]:   File "/usr/lib/python3.7/site-packages/deluge/argparserbase.py", line 329, in _handle_ui_options
Jun 22 21:00:22 htpc deluged[21885]:     _file.write('%d\n' % os.getpid())
Jun 22 21:00:22 htpc deluged[21885]: TypeError: a bytes-like object is required, not 'str'
Note: See TracQuery for help on using queries.