| Re: [AD] patch for config.c |
[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
- To: alleg-developers@xxxxxxxxxx
- Subject: Re: [AD] patch for config.c
- From: Chris <chris.kcat@xxxxxxxxxx>
- Date: Wed, 10 Nov 2004 16:13:59 -0800
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=mJGyzJsAvcaZLtWEencXCJbtTGLGKfNRDgMtzWV92UiTPdzlhvr2MvEhedZRl3Nv05p47zjJLxaNSkywmQJ1PJDdP9p8pGM4cfWp5Xq8lMeP9CyH0L+NG5cnWMquFx8xLvuwFbJcOV91hw/psmtJ1T3oD/3X8ewh4Thb7Zj+/5U=
On Wed, 10 Nov 2004 19:50:32 +0100, Elias Pschernig <elias@xxxxxxxxxx> 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.