PICARD-1045: Check for new version #902
Closed
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
… type is unknown That can happen if a new cover art type is added in MB that Picard doesn't yet know about. Instead of raising a KeyError (and crashing), just return the raw type, which is good enough until we have something better to show.
Add a framework for checking program updates by scraping the latest release version information from the Picard home page. Add manual check to toolbar under the "Help" section. Partially address PICARD-1045: Check for new version
Add a framework for checking program updates by scraping the latest release version information from the Picard home page. Add manual check to toolbar under the "Help" section. Partially address PICARD-1045: Check for new version
Conflicts: picard/ui/mainwindow.py picard/util/checkupdate.py
Conflicts: picard/ui/mainwindow.py picard/util/checkupdate.py
PICARD-1277 (workaround): translate_caa_type: Return the input if the type is unknown
|
Somehow I seem to have totally screwed up the git history on this. I'm going to close this, re-fork the repository and re-apply the requested changes. |
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.
Summary
Problem
There is currently no system included to allow checking for available updates, and for automatically notifying the user when a new version of the software is available.
Solution
Added update checking class, which calls the GitHub api to get the latest available versions (i.e.: stable and beta) for Picard and compares them to the version of the currently running instance. If an update is available, the user will be shown a dialog box with an option to download the new version.
Added a manual call to the update checker under the Help section of the main toolbar.
Added two new checkboxes to the General options tab to enable automatic checking during program startup, and whether to also check for beta (dev) versions. Automatic checks will be silent and not display check results if no update is available.
Added one new spinbox to the General options tab to select the number of days to wait between automatic update checks during program startup.
Action
No additional action required.