We now allow the backup to fail gracefully when partial files
fail to be restored. But the user is not actively informed by
these failures. Leaving him/her unaware of the state of his
configuration folder.
This commit show's a message windows, listing the failed files.
Due to a string freeze at the moment we reuse the following i18n
message:
> The following error occurred while trying to restore a Cura backup:
followed by a list of files that fails to be restored.
Which is not ideal, but a sufficient warning in my opinion. At least
better then being completely uninformed.
Contributes to CURA-8313
Sometimes, while a backup is being restore, one of the files in the current config folder may be still in use. This means that once the backup tries to replace this file with the one in the backup, the entire backup restoration fails and half the configuration folder has been messed up.
To prevent that, we decided to ignore files that are currently in use while restoring a backup. This _may_ lead to a slightly wrong configuration (e.g. a plugin may not be restored properly), but it is an acceptable result, as the rest of the configuration folder is restored properly.
CURA-8313
Revert "Change file extension to .umm"
This reverts commit 56db7f7144.
Revert "Re-enable compression"
This reverts commit 62bc9be22b.
Revert "Add documentation"
This reverts commit e9031f1aff.
Revert "Fix writing bytes to string-stream"
This reverts commit 66b2825a66.
Revert "Hide button entirely if no export is available"
This reverts commit ec727e1068.
Revert "Basic implementation of exporting all materials in a .zip archive"
This reverts commit bdcaef134f.
Revert "Implement default path for exporting all materials"
This reverts commit e66783664b.
Revert "Implement a sync button and file dialogue to export all materials"
This reverts commit abba3bdd10.
Revert "Add notion of whether printers support the material export archive"
This reverts commit f436cb8e7b.
Turns out that when the KeychainDenied error is raised, it is being caught by the macOS keyring api and the non-macOS-specific KeyringLocked error is raised instead, so we need to catch this one.
CURA-8332
To prevent the UI from being frozen. This way, the user knows that something is happening in the background and Cura didn't just stop working.
CURA-8313
Previously, after pressing the "Restore" button of a backup, there was no indication about it being restored. This commit changes that by making the "Restore" button of that backup display the busy rotating wheel.
CURA-8313
Before calling the illuminate, we need to make sure that the previous cached Preferences have been overridden by the newly restored preferences from the backup. Otherwise, the `illuminate()` function will bring back the cached preferences and the new ones from the backup will be lost.
CURA-8313
In some buttons (specifically, the "Manage printers" button), the tooltip arrow is being drawn even though the tooltip text is empty. This commit fixes that by making sure that the background rectangle (PointingRectangle) of the tooltip is not be visible if the height of the tooltip is 0.
CURA-8334
Because we're adding a messgae for the user if the loading of a plugin failed
(which can happen after backing up a plugin in central storage), we can re-enable
the backing up of plugins again.
CURA-8313
Discussed with UX what the best approach would be.
Both came to the conclusion that this is the simplest
and more aesthetic approach.
The extra white space at the bottom and height of the
first screen is still acceptable according to UX.
Contributes to CURA-8290_whats_new_text
We want to keep it this way so people can still make plugins work for older versions of Cura, like 3.6, where the 'api' field with just a single major version, instead of the 'supported_sdk_versions', which can be either a version-string like '7.6.0' or a list of version strings.
