> > It's not quite as simple as it sounds.
>
> > Where do you create the INI? Current folder? How do you handle this without the
> possibility of dumping INIs all over someone's hard drive by loading from current
> folder fails? A specific location? What location?
>
> > How do you make that platform independent so that it works reasonably AND
> consistently on Linux, Windows, Android, OS X, and your cousin's toaster while not
> breaking any existing weird setups users may be using?
>
>
> .......um, the resident directory, of course. (Current folder what? Ain't never
> happened to me.) Or, WAIT FOR IT, why not include a default ini in the package?
Yes, and then wait for the pissings and moanings of people who unzip the entire archive straight to their installation directory, obliterating the artisanally-handcrafted .ini file in there that they've been curating with love for X number of years.
There's no perfect answer to this. What problem are you trying to solve that can't be achieved (at present) by use of -createconfig?
|
Index 
Flat 
Re: Why doesn't MAME Auto-generate a default ini on unpacking?....
Reply
