DOSBox 0.74 Options
[sdl]
mapperfile: File used to load/save the key/event mappings from.

It can be loaded with a custom conf file using the [-conf] parameter.

Yes i'm aware but you can only specify the map file's name it still looks in an absolute path defined for settings (like for conf preferences).

I would still be able to load any .map file located anywhere on my disk at launchtime without having to modify the .conf file. I hope its possible. 😦

I thought you can use a different path, haven't tried on osx though.

you can load the mapper file anywhere on your system, as long as the path is correct (when you have spaces in the path you need to place the patch in "").
And if you couple this with the -userconf setting and a conf that only overrides the mapper setting you have what you want, through an additional file.

Use configuration file that only specifies the mapperfile you want to use.

TommyGun wrote:

I would still be able to load any .map file located anywhere on my disk at launchtime without having to modify the .conf file. I hope its possible. 😦

Can you give an example of what you want to do and how the current method is insufficient?

I see what he means and he is right IMHO that this would be nice.
Instead of having to edit a/the conf file just start dosbox with the commandline "dosbox -mapper mysuperduperawesomekeymapper.map". Right now, when you want to override the usual mapper file you need to do it like I wrote and use a different conf file with the mapperfile line added...
Nothing I would lose sleep over and would fight the devs over 😀

Yes correct thats exactly what i mean. Just also add this command line parameter to work as is for ease of use. For those who dont need it just dont use it but would be nice to have. 😀

This patch does most of it. Unfortunately, due to the random placement of the various codes for discovering filenames, it's more of a hack than it properly should be.

The flowcontrol is setup right, but the code inside of the "I found a -map cmdline option" needs to be fleshed out, so that if it finds the file, it says "goodie, I'll use that", then if that fails, then go to the config_path.

And of course, if any of that fails, it should probably take the "mapper" config entry...

But this is a good start, and it shows where the code needs to go...