Bug 115711 - changed settings in an external core don't get saved
Summary: changed settings in an external core don't get saved
Status: RESOLVED WORKSFORME
Alias: None
Product: kmldonkey
Classification: Applications
Component: general (show other bugs)
Version: 0.10.1
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: Petter Stokke
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-11-05 03:06 UTC by Peter Eisentraut
Modified: 2006-04-02 11:50 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Peter Eisentraut 2005-11-05 03:06:05 UTC 
Version:           0.10.1 (using KDE 3.4.2, Debian Package 4:3.4.2-4 (testing/unstable))
Compiler:          Target: i486-linux-gnu
OS:                Linux (i686) release 2.6.12-1-k7

If you change a setting in a remote mldonkey core (say max_hard_upload_rate or anything else), and then press "OK" in the dialog and open it again, the setting appears with the original value.  In other words, the mldonkey configuration dialog seems only useful for viewing, not for editing the options.
Comment 1 Christian Muehlhaeuser 2006-04-02 11:50:37 UTC 
can't confirm. though, what happened to me once: i forgot to press enter when finished changing the value and instead of this clicked on "OK" straight away. this way the value won't get saved: you _have to_ confirm the change with enter first!

please reopen, if you can confirm, that it wasn't that mistake and the error persists with the latest kmldonkey version!

thanks,
muesli