Home Page Forums MAME QMC2 Fist look for .qmc folder in working directory

Well title says it all.
I read that other thread about QMC2 portability and realized, that if QMC2 init was a bit smarter, it wouldn't (in most cases) need a parameter to define own .ini location.

Instead of using user home as first location for .qmc directory, it should first look in OWN working directory if the path exists.
OR if you want to keep user home as first location (which also makes sense), at least change the behavior so that if there is no .qmc in user directory, to then look for .qmc in working directory and use that AND ONLY IF there is no .qmc in working directory to then create .qmc in user directory.

This is a way more normalized process, that will allow for much more easier portable setups (with the help of relative paths in the config - as already allowed, which IIRC was also my request years ago and you implemented).

Your proposal isn't even the usual (or right) way on Windows ... whatever "smart" way you want can be realized with the "-config_path" parameter. The default behavior is following a platform-independent and commonly used concept.

His proposal is similar to what MAME does, actually. On Windows, it looks in the EXE directory (I should fix that to know about C:\Users\foo\Documents\My Games\MAMEdev\MAME sometime) and then in a folder named "ini" in the EXE directory. On Linux it looks in $HOME/.mame/ and then the EXE directory and then the ini folder. On Mac it looks in $HOME/Library/Application Support/MAME/, then $HOME/.mame/, then the EXE directory, then the ini folder.

One could start MAME or QMC2 from anywhere (CWD-wise), but I wouldn't want it to search for the config in the CWD - except when the user starts it with "-config_path ." for example. Anyway, my point is that the "-config_path" option is the only thing you need to specify if you want it differently than what the default does. I actually don't see why this appears to be a problem to some users.

Transparent portability is the answer.
I explained rather thoroughly in initial post (as I am usually doing even when not asked to).
Anyway, your prerogative.

You can just include a batch file that runs QMC2 with "-config_path ." to get the results you're looking for. I'd prefer if he matched MAME semantics, but it's not the end of the world if he doesn't.