Bug 168289 - kget Settings=>ConfigKGet=>Folders config'd default folder for type *, still prompts for DestinationFolder
Summary: kget Settings=>ConfigKGet=>Folders config'd default folder for type *, still ...
Status: RESOLVED FIXED
Alias: None
Product: kget
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR wishlist
Target Milestone: ---
Assignee: KGet authors
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-08-04 02:09 UTC by Roland Latour
Modified: 2008-09-14 14:53 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Roland Latour 2008-08-04 02:09:14 UTC
Version:            (using KDE 3.5.9)
Installed from:    Ubuntu Packages
OS:                Linux

Specifying a default folder should allow download without prompting for
destination folder. As-is, NFG for use with KAlarm for unattended
downloads. Workaround: use wget. So why have a GUI at all?
Comment 1 Lukas Appelhans 2008-08-04 15:33:40 UTC
Well actually the default Download-Folder is actually a suggestion in the NewTransferDialog...

Lukas
Comment 2 Roland Latour 2008-08-04 16:15:47 UTC
On Monday 04 August 2008 06:33:45 Lukas Appelhans wrote:
[bugs.kde.org quoted mail]

I went into KGet=>Help to figure out what you are talking about. I found 
Option=>UseExpertMode apparently turns off prompting. So why doesn't it say
Option=>TurnOffPrompting? For that matter, why isn't TurnOffPrompting 
available in the ConfigKGet=>Folders option-box? The user assigns a default 
directory for a filetype because he wants the program to *use* that default.
Asking for confirmation after such deliberate assignment makes no sense.

 I assume UseExpertMode/TurnOffPrompting actually refers to prompting for 
DestinationFolder, and not prompting for some other reason. Is that even a 
valid assumption?

 UseExpertMode is meaningless without further exploration by the user.
I saw a good discussion of this subject this morning, at:
      http://developers.slashdot.org/developers/08/08/03/1847220.shtml

Thanks for your attention to this matter. -Roland Latour
Comment 3 Lukas Appelhans 2008-08-04 16:26:54 UTC
Ahh no, sorry wrong version of me...

Lukas

PS: I was talking about KGet2, well I don't think this bug will be fixed in KGet 0.x.x
Comment 4 Urs Wolfer 2008-09-14 14:53:16 UTC
This works as intended in KGet from KDE 4.