[Added] Portable mode? portable.ini!

[maseter]

Could a portable mode cvar be implemented, which when set to true in gzdoom.ini, will make gzdoom use gzdoom.ini itself as the main configuration file, instead of creating gzdoom-USERNAME.ini? Because if i now put the gzdoom folder on my usb drive, and try to run it on a different PC, it will create and use gzdoom-ANOTHERPC.ini instead of using my already configured config, you see the dilemma?

I don't need a gzdoom-HOME.ini, and gzdoom-WORK.ini, and gzdoom-CYBERCAFE.ini and...

It's also a privacy issue, i thought you Germans don't just use names haphazardly, whatever happened to the whole Wie gut, dass niemand weiß, dass ich Rumpelstilzchen heiß! thing? Thanks!

Yes i know about the -config command line parameter, but still.

[NeuralStunner]

A (G)ZDoom.ini in the program directory will be used as the default configuration. But you can also specify a configuration to use via command line.

You could also use a launcher (like ZDL), or a simple batch script. Here's a one-liner for Windows:

Code: Select all • Expand view

@GZDoom -config ".\GZDoom.ini" %*

[Rachael]

Something you can also do is go into the admin command prompt and type the following commands:

Code: Select all • Expand view

move /y gzdoom-%username%.ini gzdoom.ini
mklink gzdoom-%username%.ini gzdoom.ini

The first command is simply a rename (with overwrite) and the second command creates a symbolic link to gzdoom.ini. You can change %username% to all the different usernames you use on your work machines and make symbolic links for each of them.

Symlink functionality is available in Windows Explorer (it will recognize them and display them as shortcut files), but Explorer cannot create them by itself.

[maseter]

Thanks for the tips, i do use -config but still .

Maybe GZDoom could check for (and use) portable.ini before creating a gzdoom-%username%.ini, problem solved!

[Graf Zahl]

I think that goes well beyond what he needs.

The reason why I haven't added this is because the config file code is excessively pedantic about PREVENTING the scenario you want. Once it has made up its mind about the config's name it will remain. And it's simply too late when it comes to do the necessary checks because in order to read the value it needs to initialize the config file, and to read the config file it needs to set up its name. And I really don't want to mess around with this any more than necessary because it may break stuff I don't even think about.

[Graf Zahl]

Thanks for the tips, i do use -config but still .

Maybe GZDoom could check for (and use) portable.ini before creating a gzdoom-%username%.ini, problem solved!

There I think about the most complex solutions, then this comes up...
I'd still put a 'zdoom' in the name, just for those who absolutely must put everything into the same directory.

[Graf Zahl]

Ok, done. The filename will be zdoom_portable.ini for ZDoom and gzdoom_portable.ini for GZDoom. I intentionally used an underscore to avoid clashes with people who happen to name their account 'portable', which I do not consider out of the option.

[maseter]

[maseter]

Good news, this is now implemented, gzdoom_portable.ini, as of today's build:
http://devbuilds.drdteam.org/gzdoom/gzdoom-g2.2pre-1504-g47064e2.7z

But it does not inherit gzdoom.ini settings, like gzdoom-USER.ini, just fyi, i guess that's intentional?

[Graf Zahl]

Yes, that's intentional. How else should it work? The portable ini file needs to be present in order to be used, so that obviously rules out loading the generic one.