Right now when a custom version string is used (via SHOTCUT_VERSION=) the new version notification still shows up. The problem is that shotcut checks if the application version and the last version is exactly the same. That results in the new version notification being triggered even if it's already in the last version (Ex. 18.08.14-ARCH != 18.08.14). IMO we have two ways to fix this, the first would be disabling this feature when a custom version string is used, this option is almost only used by distributions so that would actually be a good thing, or change the check to see if the custom string contains the last version string, this might not work depending on the custom string model.
Thank you,
Filipe :)
Right now when a custom version string is used (via
SHOTCUT_VERSION=) the new version notification still shows up. The problem is that shotcut checks if the application version and the last version is exactly the same. That results in the new version notification being triggered even if it's already in the last version (Ex.18.08.14-ARCH!=18.08.14). IMO we have two ways to fix this, the first would be disabling this feature when a custom version string is used, this option is almost only used by distributions so that would actually be a good thing, or change the check to see if the custom string contains the last version string, this might not work depending on the custom string model.Thank you,
Filipe :)