wtf keys have different names there ?!
When we have an option to decide what keys we want to use, I believe they should be clean and self-explanatory.
amule.conf is a big mess as it is now. If you first saw "PasswordLow", what would you think it is for?
Unfortunately we can't expect to clean up amule.conf, because
1) backwards compatibility
2) eMule compatibility
Still this doesn't mean that we have to clone this mess on a new config file.
We have dedicated config file for remote tools, called remote.conf - lets be consistent and use only this one.
People may want to access amule core on more than one computer from the same computer (not necessarily at the same time), so we have to provide means to use any file as a config file. "remote.conf" is just the default.
I think easiest way would skip step (2), i.e. pressing OK button should update content of remote.conf.
I don't agree. Why should an application (over)write the configuration file of another app?