Conflicts:
resources/definitions/skriware_2.def.json -> File was rewritten while I modified the platform mesh. All indentation was changed to tabs which caused a merge conflict.
The following changes have been done:
- Text content changed
- "Sign in" and "Create an account" buttons moved in the middle,
under the main text
- "Sign in" button changed to PrimaryButton format
- "Finish" button changed to "Skip"
- "Skip" button format changed
CURA-7019
If the user signs in during the welcome process, if he/she has cloud
printers connected to his/her account, then the welcome wizard will
close so that the user will not be asked to add local printers.
CURA-7019
The renderer isn't active when the view is activated. As such,
no opengl context *ever* exists. In some cases this might cause it to get
stuck in an indefinate loop.
The comments around it are explaining a situation that can't occur. The activateView
event of SolidView isn't triggered when switching to another view...
Otherwise if a retracted move had a different Z coordinate, this would not be put in the final print. It's pretty simple to extend it this way.
Fixes#7458.
It was doing an os.path.exists on the relative path which has no context of where we're looking from. So make it absolute first and then check for the existence of the file. Also take the correct parent folder then and improve debug output.
The import script doesn't parse these correctly yet. Keep finding them now.
Some of the plural forms were incorrect. They were like that last time as well. Lionbridge isn't translating them correctly, but it's the fault of a very annoying interface in Smartling. I was able to fix all of them decently except Russian, so Russian will have to make do with just plural everywhere.
Contributes to issue CURA-7344.
These are the new translations we got. I didn't make any corrections yet, but I did already see some mistakes in the Chinese ones.
Contributes to issue CURA-7344.
I don't know what exactly caused this since it's impossible to trace. But the crash happened with a setting called 'dual_gcode' which currently doesn't exist in Cura. So I think it must be some plug-in that adds it. In any case, it's good to be defensive about this sort of thing. Good type checking would've caught this for us.
Fixes Sentry issue CURA-JB.