-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Adding better parameter handling #22
Comments
.ini files are now supported with the following syntax:
The .ini file should lay at the top program folder. |
If there is just one .ini file with a fixed location, how can I start several configurations without changing the .ini file(s)? |
At the moment it is not possible, but I can add different path support in the next days. |
No hurry. I noticed that I can use it with the command-line options for now. |
Now it is possible to give the path to the .ini file as command line parameter. So you can create different links to the executable and run different configurations. If no parameter is set, it will try to load the options.ini file in the executable's main directory. |
I got parsing errors with the following ini file:
Can you give an example how the file is supposed to look like or correct the above example? |
Should now work. Seems Windows needs a special format other than Linux. Should be fixed now on the dev branch. My configuration ini looks like this on my Windows machine:
|
Took me a while to find out that [options] is required and that you changed the order of two parameters. ;) Seems to work fine now. Good job! :) |
We should improve the parameter handling through a config file or flags in the command line call.
This makes it even easier with optional parameters.
The text was updated successfully, but these errors were encountered: