| [AD] New config function suggestion |
[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
- To: alleg-developers@xxxxxxxxxx
- Subject: [AD] New config function suggestion
- From: "Ryan Patterson" <cgamesplay@xxxxxxxxxx>
- Date: Wed, 8 Mar 2006 21:34:38 -0500
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=aeHjuet+aE9sGbY/qyFFyYyRfM71UFypSb6e/h3/fB2vRkJMBSn1a5YMe3WDV2PPRaVIyS4n/byPc7IHCQS4uIDng7kqvb4Vuxb3J5xQDnl/gb+19HX1Riu9GMvONEuOGkJjcRlOokh1e5Gm0YiBqnf2B8NN7fXSleHDjKYZa1k=
I have an idea for some new config file functions, and I would like to
know if I wrote them if they would be eligible for inclusion in the
current Allegro tree...
{get,set}_config_key - These do the same as config_int, except that
they store the value as a string like KEY_A in the INI file, and
automatically convert.
{get,set}_config_color - These would read or set a color in the INI
file. The color could be in the form of hex #ffffff, or decimal 255,
255, 255. (Conversion at call of function)
{get,set}_config_card - These would read or set a graphics card name
in the INI file. It would appear in the ini file as (for instance)
GFX_AUTODETECT, and automatically convert.
--
Regards,
Ryan Patterson <mailto:cgamesplay@xxxxxxxxxx>