Skip to content
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

Settings file location hard-coded #169

Open
Rezzy-dev opened this issue Sep 20, 2022 · 0 comments
Open

Settings file location hard-coded #169

Rezzy-dev opened this issue Sep 20, 2022 · 0 comments
Labels
bug Something isn't working enhancement New feature or request

Comments

@Rezzy-dev
Copy link

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.

@jtothebell jtothebell added bug Something isn't working enhancement New feature or request labels Oct 13, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants