Build Your Own Arcade Controls Forum
Main => Software Forum => Topic started by: RobotronNut on April 14, 2006, 08:37:27 pm
-
i've been using controls.ini, johnny5, and mamewah with good success. (btw, thanks to all the developers who put all that together!)
i've been tweaking controls.ini in ways that suit my particular situation but would not be appropriate to contribute back to the project for general use, because they violate the controls.ini guidelines.
i'd like to be able to take future releases of controls.ini, while retaining my changes. is there a recommended way of doing this? i can think of a couple of possibilities:
(1) keep my stuff in a separate file, which i just prepend to controls.ini whenever a new version comes out. for now, j5 is the only program that i'm using that reads controls.ini, and i'm guessing that it just reads the file from the beginning and stops as soon as it finds the entry it's looking for, so having duplicates would be no problem (first one wins). is that a good assumption?
(2) use a source code control system and let it perform automatic merges with manual conflict resolution. this would be more cumbersome but might work better if the file format itself changes a lot.
i'd appreciate any suggestions anyone may have about this.
-
First off.... http://fe.donkeyfly.com/forum/index.php?topic=119.180 (http://fe.donkeyfly.com/forum/index.php?topic=119.180)
Yes J5 generally just reads the first entry to match, however it uses window's "readprivateprofilestring" which does the searching automatically, so how exactly it finds a match is a bit of a mystery.
The format wont be changing anytime soon barring the occasional addition of a control type. Sirp and I went to great lengths when designing it to assure ourselves that we would have to redesign the format later on.
-
sounds good. i'll give the simpler method a try. thanks.
-
i've tried the simpler method ("keep my stuff in a separate file, which i just prepend to controls.ini whenever a new version comes out"), and it works just fine.