Re: [Bug-gnubg] Setting default board colour scheme

[Jim Segrave]

On Fri 13 Dec 2002 (11:11 -0000), Ian Shaw wrote:
> > 
> > The problem is that you can extend these arguments: we want a seperate
> > file for evaluation settings, and a seperate one for rollout settings,
> > and a separate one for paths etc. We may end up with tens 
> > or hundreds
> > of different settings files, so setting X can be stored 
> > independently from
> > setting Y.
> > 
> True; it would open up a whole can of worms, which you probably want to avoid 
> at this time. OTOH, this is how most Windows programs operate, so a lot of 
> users are used to it. I don't see any need to create hundreds of different 
> files. You could retain one file, but only edit the relevant entries. This 
> seems to be the case with many Windows programs that use an .ini file. 
> 
> It should be noted that one of the main differences is that in the Windows 
> world, the .ini file is automatically updated when the setting is changed. 
> I.e. the setting applies thenceforward; not just for the session. There is 
> therefore no need for a Save Settings at all.
> 
> This may or may not be desirable for gnubg, nor do I have any idea about the 
> Unix world standard. I suppose this is a matter of design philosophy.

I'd be inclined to do the following:
Have a 'save changes' option which writes only the changes since the
last 'save changes'. If there already are saved changes, give the
option to merge them into the .gnubgautorc file or overwrite them.

I often am playing with odd settings for an evaluation or similar and
I never want those kept as a startup configuration. 

Another useful feature would be to allow a small level of nesting of 
include files in gnubgautorc. Then users could change which board
design/set of evaluations or whatever they wanted to use while
retaining the unchanged settings.

-- 
Jim Segrave           address@hidden