You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What are the steps needed to delete meta data for a profile and for deleting a game from ModaBuddy? Currently, I reset the whole application by deleting everything in the games directory and deleting the settings.json.
It would be better for testing and maybe user organization if the games directory was for saving base things about each game added, and then a profile directory for each profile made. I am assuming a bit of metadata to tag which game each profile goes to. This may or may not result in deprecating the settings.json file, which is my goal because its nice to delete just files rather than edit them for resetting an application.
This question/suggest are just that, you may have design choices in mind that want to stick to the current file architecture.
The text was updated successfully, but these errors were encountered:
That would be the correct way to purge all user-settings, and i agree to it not exactly being "ergonomical".
The current design choices is mostly to keep my options open and keep it simple enough. In other words, the current setup with user data is mostly grown "organically" to solve another need at the moment.
What is the other need? I would rather not sink time into a proposed alternative if that alternative doesnt solve the immediate need in the forefront of your mind.
I didn't mean a literal need, but that it has grown in regards to other stuff, the last one being multiple profiles pr. game. But creating a file architecture that reflects the inner workings of this GUI could be advantageous.
What are the steps needed to delete meta data for a profile and for deleting a game from ModaBuddy? Currently, I reset the whole application by deleting everything in the
games
directory and deleting thesettings.json
.It would be better for testing and maybe user organization if the
games
directory was for saving base things about each game added, and then aprofile
directory for each profile made. I am assuming a bit of metadata to tag which game each profile goes to. This may or may not result in deprecating thesettings.json
file, which is my goal because its nice to delete just files rather than edit them for resetting an application.This question/suggest are just that, you may have design choices in mind that want to stick to the current file architecture.
The text was updated successfully, but these errors were encountered: