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.

Sign up for GitHub

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

Jump to bottom

Feature: change the way settings are stored/saved #62

Open
Zutatensuppe opened this issue May 1, 2020 · 0 comments
Open

Feature: change the way settings are stored/saved #62

Zutatensuppe opened this issue May 1, 2020 · 0 comments
Labels
Feature

Comments

@Zutatensuppe
Copy link
Collaborator

Settings that are only tooling related (http client, pipe server, etc) should be stored separately from the run related settings (autosplits, rune settings, etc.). Or at least "settings changed" should trigger separately and only if the according section actually changed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Feature
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@Zutatensuppe