On Wed, 20 Oct 2010 12:25:46 +0100 Nick Treleaven nick.treleaven@btinternet.com wrote:
That'll take some time to write, for example to check that all changes are applied immediately, but I'm willing to do it, if you think it's a good idea. The stash provides a good base for such an interface.
It would be nice for the user. However, it would mean all hidden prefs would need to be made reloadable. I don't want to do that really.
Yes... Some settings will probabbly work automatically, for example editor ones, and others may be easily reloadable, but I too don't want deep changes just to make _all_ prefs "appliable".
You're right, perhaps we could separate hidden prefs that need restarting and those that don't.
Here I meant having two hidden pref stash groups, one for prefs requiring restart and one not. keyfile.h could expose them so other files can use them.
I wasn't thinking about visually separating the prefs. Perhaps this could be done by having 2 different treeview parent items, rather than having to switch tabs (as Lex suggests). That way the user can see all hidden prefs on screen at once. But visually separating 'restart' prefs is a refinement of the feature and could be done later.
Also, I think the feature code should be in a separate file, not prefs.c.
Nick