Don't know how long we support opening images, but this commit adds them to the *.desktop file for Linux based desktops.
So "open with"-actions will now show Cura for these media-types.
This preference can't be made visible since a string freeze is into effect, but at least a user could go into the .cfg file and set the setting manually.
Contributes to issue CURA-611.
The default preference for last remembered output file type is set to G-code. So at the first run, it'll have g-code selected by default. In subsequent runs it will remember what the setting was, so the user can set it to something else and it will remember that.
Contributes to issue CURA-611.
so it is more clear when JobSpecs uses the fileBaseName from cura_app.py and when it uses fhe fileBaseName from cura.qml
Contributes to #CURA-707
Contributes to #CURA-620
#591
or something alike for instance when the file is dragged onto the logo(MacOS) or with 'open with'(Windows)
Fixes to #CURA-707
Fixes to #CURA-620
Fixes#591
Instead of having a list of languages hardcoded, we scan the i18n directory for available languages.
It was a TODO, which was left after fixing po-file installation. After finding the macro I decided to fix it here.
The reference to the added macro is there as an URL.
If the legacy profile contains float values serialised to '0.0' or '0.00' instead of just '0', this now works correctly instead of evaluating the string comparison to false.
Contributes to issue CURA-37.
If the eval failed that is likely caused by a variable not existing. It now continues with evaluating other settings and just doesn't add the setting that depends on non-existing legacy settings. This happens when the imported profile is not complete or corrupt.
Contributes to issue CURA-37.
In the evaluation that's passed from the Dictionary of Doom, the settings are still strings so you can only parse the settings as string...
Contributes to issue CURA-37.
Retraction combing was an enum (a fact which was not documented). This enum must be parsed to a boolean. The 'no skin' option now evaluates to true since it is not implemented in the new Cura.
Contributes to issue CURA-37.
Something that was not in the translation document: If a speed setting for a specific part is 0 (such as infill_speed) then the global print speed should be used.
Contributes to issue CURA-37.
So the translators know in which groups to group the menu-items. The reason for this is that the translator choose alt key accelerators that are unique within its own group.
Contributes to #CURA-526
