Exported ints and RestartGame

Started by Bernie, Fri 26/11/2004 02:25:36

Previous topic - Next topic

Rui 'Trovatore' Pires

QuoteYeah, I can see the uses for that. Would anyone else find this a useful feature?
Well, since ease of use is a common goal, I'd say it has my vote. It's nice to know it's there if I ever need it (don't know if I ever will, though, tell the truth and shame the bad red guy in pitchforks).
Reach for the moon. Even if you miss, you'll land among the stars.

Kneel. Now.

Never throw chicken at a Leprechaun.

RickJ

Re: Read/WriteConfigOption()

I guess I would find it useful having an easy way of working with M$ ini files if that is what is under consideration.   I prefer to leave the AGS config file alone and use another file for the kinds of things discusse so far.   So  then may I propose the following suite of functions in place of the previously suggested Read/WriteConfigOption() functions.  Thanks.

OpenConfigFile(string filename)
ReadConfigStr(int id, string section, string option, string value)
WriteConfigStr(int id, string section, string option,string value)
ReadConfigInt(int id, string section, string option)
WriteConfigInt(int id, string section, string option,int value)
CloseConfigFile(int id)


Pumaman

Hmm I don't know, it all seems to be getting a bit much for the value of the feature. Config settings can always be stored using the File I/O routines, and although I can see the ease-of-use benefits of having some sort of Read/Write Config this all seems to be getting a little involved.

RickJ

I can't really disagree about doing it with the existing File I/O functions. 

It's a shame there isn't some kind of script module thingy where a moudle could contain a collection of functions, variables, etc and where modules could be included or installed to extend the AGS internal functions.  ::)  I know you've been thinking about it so I'll stop short of asking.    :-X


SMF spam blocked by CleanTalk