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

Create a default Supermodel.ini and Games.xml if they don't exist #45

Open
casasfernando opened this issue Nov 15, 2022 · 2 comments
Open

Comments

@casasfernando
Copy link
Contributor

When a user runs Supermodel for the first time or if for some reason the Config directory is not available in current Supermodel binary path, Supermodel fails to start because of the missing Supermodel.ini and Games.xml files.

It would be great if Supermodel can automatically create these two mandatory files in case they are missing.
This is sort of related to #6 so implementing this can solve that one as well.

Thanks.

@trzy
Copy link
Owner

trzy commented Nov 18, 2022

We can remove the INI and XML file from the Config/ subdir (what happens when you extract a ZIP file with a subdirectory in a directory where it already exists but has more files than the ZIP file does?) and move them into a header file as string literals, similar to how shaders are handled. Then they can be directly emitted if necessary.

@kathyrollo
Copy link

kathyrollo commented Oct 18, 2023

Hey @trzy , accidentally overwrote the Supermodel.ini again during update. Having to manually delete the default .ini from the archive every time before extraction/drag-n-drop is overall not the ideal UX, since it is very easy to forget even for seasoned users. The config system is already a learning curve for most users, and having it overwritten so easily can make them even more frustrated with an emulator they are already weary of due to its cmdline interface. I personally do not have the energy right now to re-create my own config. Have to refer to my own video tutorials haha.

Would be great if the above you mentioned can be implemented. Ideally, an app should always generate its config files when they do not exist, and do not generate them when they exist. With this behaviour, whether the .exe was executed for the first time or not becomes irrelevant, as the first thing the app will do is check for existence every time it is run. Most standalone emulators also do it this way.

Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants