Fix save location of custom mineral systems #287
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ored to avoid loss when updating, add path util funcs
nmaarnio
added
bug
msorvoja
approved these changes
Nov 28, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Changed the save location of custom / user-defined mineral system JSONs from a directory under the plugin to a directory under the QGIS profile the user is using. This should fix the unwanted behavior where custom mineral system JSONs get wiped out when updating / reinstalling the plugin.
Unfortunately the custom mineral systems users have defined right now need to be exported manually and imported back after the next release of EIS QGIS Plugin. Automated migration is not possible because the migration code would run only after updating the plugin, when the mineral system JSONs are lost already 🙁