#2012: "Download location" bug
------------------------+---------------------------------------------------
Reporter: Redsandro | Owner:
Type: bug | Status: closed
Priority: minor | Milestone: 1.3.x
Component: gtkui | Version: 1.3.3
Resolution: wontfix | Keywords:
------------------------+---------------------------------------------------
Comment(by Redsandro):
The same logic (as ticket #2013) applies imo to every way of changing the
`download_location` for a single download. GUI, Web-UI, Terminal, or
through plugins like FlexGet. No matter in what way you add and control
your downloads, ''forcing a two step process to edit moveto after the
torrent has started'' is always going to be illogical, and new users will
probably always make the mistake of thinking Deluge will deduct from a
changed `download_location` that the default `move_completed` has been
obsoleted.
I'm not trying to be annoying here, because for me personally I can work
with Deluge just fine now that I know about this. But I like Deluge, and
it's little annoyances like this that seperate good software from great
software.
--
Ticket URL: <http://dev.deluge-torrent.org/ticket/2012#comment:12>
Deluge <http://deluge-torrent.org/>
Deluge project
--
You received this message because you are subscribed to the Google Groups
"Deluge Dev" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/deluge-dev?hl=en.
