Basically we should never be raising the master Exception class, really.
The enclosing class has error handling in case this returns None already, so this fix is easy.
Contributes to Sentry issue CURA-Y5.
When printers share the same group_id, they are removed, regardless if
they are hidden or not. This was resulting in sometimes removing
multiple printers when removing a printer that was created by a project
file.
This PR fixes that by actually checking whether the printer to be
removed is hidden.
CURA-7522
Even though the metadata of the machine was updated when it was
rediscovered, the new cluster id was not updated in all its references
(such as in the _remote_clusters and in the _um_cloud_printers dicts).
This commit fixes that issue by properly updating all the entries
that depend on the machine's cluster id.
CURA-7505
to "Account synced"
Don't think the duplication I found is necessary, but I don't dare to
deduplicate it as I found some logic inconsistencies
CURA-7418
This fixes the issue of the "Select configuration" label appearing on
top of the extruders in the configuration menu. This could be observed
when adding a UM2 with Olsson block.
The SystemPalette was not properly reflecting the text color in the
dark theme (the icon remained black). For that reason, the palette
is removed and color for the icon have been added in the themes.
CURA-7418
The following issues are fixed:
* The visibility of the placeholder rectangle, according the existence
of the avatar image
* The initial letter not being visible in the dark theme
* Vertical alignment of the avatar
CURA-7418
It was aligned to the bottom side of the build plate rather than the top side. This build plate is 3.2mm thick, so to prevent Z fighting I'm moving the model 3.3mm down.
Contributes to issue CURA-7515.
Since the host_guid is unique to the printer, it is more reliable for
identifying the cloud printers. This comes in handy when the cloud
printer is removed from the account and re-added. With the host_guid,
the printer that is added again can be properly identified as an
existing Cura cloud printer, and be linked to the original. To
achieve that, the META_CLUSTER_ID of the printer is updated with the
new one that is generated when the printer is added again to the
account.
CURA-7505
