Re: [AD] patch for config.c

[Chris <chr...@gm...>]

On Wed, 10 Nov 2004 19:50:32 +0100, Elias Pschernig <el...@us...> wrote:
> >From writing to the global allegro.cfg, which makes no sense IMHO, to
> writing into my.cfg. The reason to not use set_config_file instead of
> override_config_file is so subsequent calls to e.g. set_video_mode will
> be able to read global settings from e.g. /etc/allegro.cfg, and not try
> to read from my.cfg which won't have that information.
> 
> Also in the case a program actually updates things like the used gfx
> driver, it makes more sense to write it into "my.cfg" than into the
> global config, where it suddenly affects all allegro programs.

This seems to be my biggest beef with the current config system.
There's no way I can use the original allegro.cfg loaded by
allegro_init (or wherever), but also have another mygame.cfg that can
override some of those values with game-specific ones, and to have
new/modified values written to mygame.cfg (they would go into
allegro.cfg). If this is what that patch allows, I'm all for it.