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

Allow local settings and relative SongDir paths for portable USP installations #502

Open
JakobStaudt opened this issue Nov 8, 2024 · 1 comment
Assignees

Comments

@JakobStaudt
Copy link

Issue type: Feature request

Actual behaviour

Ultrastar Play on Windows uses the AppData directory to store its config data (Settings.json etc.).

Expected behaviour

For some applications (mainly a portable USP installation on an external drive that should be usable on multiple computers), it would be useful to have the settings located close to the USP files. This would allow the settings to be persistent across computers, if the external drive is connected to other computers. It would also be necessary to allow relative paths for the SongDirs, so mounting the external drive (containing USP and songs) as a different Drive Letter doesn't break the SongDir settings.

Implementation hints

On Startup, USP should check if the USP directory (or its parent?) contains a settings dir as it would normally be found in AppData. If a settings dir is found, it should be used, and no directory in AppData should be created. Only if no local settings are found, the AppData folder should be used/created.
The SongDirs Setting should be able to use relative paths. Ideally, the paths specified should be interpreted as relative to the settings file (or its parent?), so the location from which USP is started doesn't affect the behaviour.

@AnsisMalins AnsisMalins self-assigned this Nov 12, 2024
@achimmihca
Copy link
Collaborator

You can already specify a custom settings file via command line argument --settingsPath.
See https://github.com/UltraStar-Deluxe/Play/wiki/Command-Line-Parameters

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