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

Linux: store QSettings in a single location #129

Merged
merged 1 commit into from
Jul 16, 2024

Commits on Jul 16, 2024

  1. Linux: store QSettings in a single location

    Fixes the Linux part of Unvanquished#121. Choose the location of our settings by
    changing the default location for settings, rather than customizing the
    parameter of our settings object. This makes it so the settings added by
    a component we depend on end up in the same place.
    
    Some more explanation quoted from the Github thread:
    
    >   I still don't understand the reasoning? Is it that the name
        "Unvanquished Development" is better on Windows?
    
    >   With the organization name, actually Mac and Windows are the same
        and Linux will now be different. Previously, we chose the
        unvanquished/updater path to store the main settings of the updater.
        Some stuff was stored in an Unvanquished Development/Unvanquished
        Updater path by accident; I want to stop that. We need to go with
        the lowercase one to maintain compatibility with the previous
        version of the updater. But yes, the lowercase ones seem more in
        line with Linux stylistic conventions.
    slipher committed Jul 16, 2024
    Configuration menu
    Copy the full SHA
    2f41ff2 View commit details
    Browse the repository at this point in the history