There are several new command-line switches which have no corresponding options in Qt:
These older switches can probably also use a config panel equivalent:
Makes a whole lot of sense to add these and I also still have that proxy-stuff in my mind (with a simplified code in init.cpp ^^).
I guess we should discuss, if some other dev is missing further options, I know @gmaxwell was looking for some more of the networking stuff.
Agreed. Though we only want the more common settings in the ui, those which can be explained to end users in a few lines. The very obscure ones that make sense to developers only can always be provided on the command line or in bitcoin.conf.
"Listen" really could use a gui option.
I still have that proxy stuff in mind, remember? When doing this a listen switch could for sure be added. But I have got one problem with Qt and networking stuff, as we currently mirror some of the code for setting the proxy, which is IMHO a bad thing. Perhaps we always should require a client-restart when changing network stuff and remove ApplyProxySettings() from optionsmodel.cpp ... thoughts?
I think the few checkboxes/fields suggested here are much more useful than making proxy settings fully tweakable from the GUI :)
Even if you separate the two and I agree, we should extend the GUI options, there is still my question open :).
Currently working on this, but it will take some time... it's a little fiddling work to be done here ^^.
-Listen and -dbcache are now changeable through the UI.
I would say -par, checkpoints, -checklevel, -checkblocks, -maxreceivebuffer, -maxsigcachesize belongs to a text-config-file (or cmd args) only.
-par is also settable in the GUI
@laanwj right. I oversaw that.
The question is if we should agree for adding UI settings for checkpoints, checklevel, checkblocks, maxreceivebuffer, maxsigcachesize or close this issue.
(IMO we should close the issue)
I agree and see no value in that. So let's close this issue.