We didn't fix the issue with plug-ins causing a crash at early start in rare occasions. We did increase logging so that we can hopefully fix it next time.
Contributes to issue CURA-8876.
But we need it opn platforms we might release an Enterprise edition for. Fortunately, Linux is not one of those platforms, so it all works out anyway.
CURA-8475
In most languages this doesn't properly fit in the space we have for these buttons.
The same text in the window title and header was not changed. There we do have space for it. The button in the material manager was also not adjusted since it's different and already about as short as can be (but needs to refer to printers instead of materials due to the context of already being in the material manager).
Contributes to issue CURA-8753.
These translations don't fit in the space we have for the button. We'll change the English text for the next release, but for this time we'll change just the translations that are giving us problems.
We'll accept that Czech and Turkish still have a bit of overlap in their buttons for this release.
Contributes to issue CURA-8753.
Conflicts:
resources/i18n/de_DE/fdmprinter.def.json.po -> Improved translations while the translation bureau made new translations.
resources/i18n/pt_BR/cura.po -> For some reason it had a conflict with the last-changed date here. Not sure why but I reverted any changes to this file.
Our import script still doesn't handle these well. But it was quite easy to fix this time since the translations were indeed present.
Contributes to issue CURA-8753.
This is currently only used in the pre-read of workspaces. In some cases, the project file may have a material that is not compatible with its own stack using the current rules in Cura, either because the rules changed or because the project file is wrongly crafted/edited. This causes Cura to say there are no quality profiles if the material profile is not compatible with the printer, preventing a crash due to the KeyError.
This has been replaced with PyClipper so we don't need to import Shapely any more. Clipper doesn't give any exceptions as far as I know.
Contributes to issue CURA-8592.
