The settings file should be read from the current working directory -- where the binary is located and run from. At the moment its location is hard-coded -- which is not a good idea. If the user moves the program to a different directory, the settings from "settings.ini" are no longer read, as if the file didn't even exist. The program keeps looking for the file in the detault install location. What more, further saving of the settings in the emulator is made impossible simply because the binary and the settings file have been moved from the hard-coded default location.
The settings file should be generated and read from where the binary is located, the program's working directory -- not hard-coded.
The settings file should be read from the current working directory -- where the binary is located and run from. At the moment its location is hard-coded -- which is not a good idea. If the user moves the program to a different directory, the settings from "settings.ini" are no longer read, as if the file didn't even exist. The program keeps looking for the file in the detault install location. What more, further saving of the settings in the emulator is made impossible simply because the binary and the settings file have been moved from the hard-coded default location.
The settings file should be generated and read from where the binary is located, the program's working directory -- not hard-coded.