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

Configure: improve defaults after rescan? #220

Open
brliron opened this issue May 16, 2023 · 0 comments
Open

Configure: improve defaults after rescan? #220

brliron opened this issue May 16, 2023 · 0 comments

Comments

@brliron
Copy link
Member

brliron commented May 16, 2023

Choosing a default game during a rescan can be hard. Yet, it's important because many users don't even know you can change the default (which is probably an UI problem, but that's another question).
If a rescan finds a new version for an existing game, I think I prefer to try keeping the old version. If this is for example EoSD or another game that keeps its save data in its own directory, choosing another game version could lead to the user losing their save data (not actually losing it, it would still be there in the previous game installation, but that's what it would look like for the end user).

On the other hand, a rescan could also happen because the user moved their games. In this case, he would prefer to have the new games. This case can actually be detected with decent reliability: if the old path doesn't exist, we shouldn't keep using it, and we can start using the new one.
... Unless the game is on an USB drive which happened to be disconnected during the rescan. In which case we would want to keep it.

Anyway, it's not as easy of a choice than it looks like at first glance, but it's worth discussing and trying to see if we can improve things.

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

1 participant