🎉 Added Portable Mode Client Command

[Linkazen]

Implementation of #1501

[Schneegans]

Thank you for this! We could use this! Yet I wonder whether a --config-directory option could be more useful.

The problem I have with --portable-mode is that it's behavior is not really intuitive (at least in my opinion). As it creates the file, any launch thereafter will also be in portable mode and there is no obvious way in going back. So even if you launch Kando without --portable-mode, it will still be in portable mode. A --config-directory would solve this as well and would be more understandable, I think.

What do you think?

[Linkazen]

Yes, I think it's a bit unintuitive too to be honest. A --config-directory flag would definitely solve this issue. The only problem I can think of, is that I think having a way to use the default (config right next to the executable) would be nice. Perhaps within code if someone gives starts the --config-directory value with / or C:/ then the program would start at root, and otherwise it's relative to the executable?

Either way I'll start looking at implementing a basic version of this, let me know your thoughts on any specifics. Thanks!

[Schneegans]

Yeah, I think a realtive path should be relative to the executable.

[Linkazen]

Alright @Schneegans, I think that should be good. Only thing I'm thinking of changing is possibly the default behaviour of the --config-dir flag. Currently it uses the defaultPortableConfigFolder value to create the config directory. But perhaps instead it should be used to reset config directory back to default? What are your thoughts.