[Feature Request]: Automatic updater on start up
Checklist
- [X] I am using an up-to-date version.
- [X] I have read the documentation.
- [X] I have searched existing issues.
Description
When not using the program after a while, it is easy to fall behind in with updating the application version.
Solution
Whenever a user starts up an instance of tag studio, it could check and compare the latest release available for tag studio and if it doesn't match the currently installed version, it will install the new version of tag studio, replace the program files that need replacing and restart the program so that it will be seamless for the end user.
some additional notes:
- it would only check at most once a day to once a week.
- automatic update checks should be an opt-in feature, but there should be a on-boarding step for the program that suggest enabling it with a checkbox.
- there should be a setting to toggle the automatic checks on or off
- the user should be able to do a manual check if there is a new version. to prevent adding too much web traffic, it could cache the result of the last hour (arbitrary amount) and use that before doing an actual check.
Alternatives
this feature request could be split up into two separate feature requests when looking at the scope of it. as checking for a newer version and replacing the old version with the up to date version are two different processes.a simple update notice would most likely already be helpful to some people.
This sounds good, but a few things:
- Portable installations - it's very likely the user wouldn't want it to automatically update, and we wouldn't necessarily know where to put the new file
- Linux users - again, we wouldn't really know where to put the file - even just with people using the standard DEs (GNOME, KDE, etc), they will be in different places (I believe), and thats not counting people who are using WMs or have even installed it from the AUR
Probably a better way to do it would be just update checking, and have TagStudio notify the user that there is an available update when there is one. I suppose we could also have different versions of the program do different things (non-portable Windows have an automatic in-place update, for example), but that sounds complicated and probably not worth the effort at this point.
I second this feature (Or third, if you're technical!!)
But instead of Auto-Updating?? How about check and inform the user if an update is available?? (I didn't get a prompt when a new Pre-Release was available)