Age | Commit message (Collapse) | Author |
|
In preparation for release of the 4.8.
CURA-7795
|
|
We're changing the unit of one of our settings, so we need to implement a version upgrade to change that for our users in case they changed this setting themselves.
Contributes to issue CURA-7118.
|
|
CURA-7641
|
|
As this will also remove them from machines that go through the VersionUpgrader.
|
|
CURA-7608
|
|
Since the metadata/setting_version field was not written in project files from the 3MF writer,
the preferences were never really updated, because their preferences version was marked as 6000000
(basically omitting the setting_version). Now, if any project file is found without a metadata
setting_version tag, it will default to preference version 6000000 and thus it will start calling
the updatedPreferences() functions starting from VersionUpgrade34to35, properly updating the
preferences and adding the metadata/setting_version field in the preferences.cfg of the project
file.
CURA-6711
|
|
is in that list
CURA-6711
|
|
|
|
CURA-6711
|
|
Related to https://github.com/Ultimaker/Cura/pull/7726
|
|
Add PostProcessingPlugin script DisplayProgressOnLCD
|
|
Co-authored-by: Konstantinos Karmas <konskarm@gmail.com>
|
|
It was decided that functionality present in existing plugins is
sufficient. No need to replicate it in our own codebase and
take on the burden of maintenance
CURA-5479
|
|
CURA-5479_job_name_template version upgrade
|
|
CURA-5479
|
|
Part of CURA-7199
|
|
Part of CURA-7199
|
|
CURA-7517
|
|
|
|
These two version upgraders do the same operation. Their code is copied. Instead, we can just let one version upgrader upgrade both versions of the files.
Contributes to issue CURA-7413.
|
|
Converted doxygen style comments to reStructuredText style
|
|
|
|
doxygen_to_restructuredtext_comments
# Conflicts:
# cura/API/__init__.py
# cura/Settings/CuraContainerRegistry.py
# cura/Settings/ExtruderManager.py
# plugins/PostProcessingPlugin/scripts/PauseAtHeight.py
# plugins/UM3NetworkPrinting/src/Cloud/CloudApiClient.py
# plugins/UM3NetworkPrinting/src/Cloud/ToolPathUploader.py
# plugins/UM3NetworkPrinting/src/Network/LocalClusterOutputDeviceManager.py
|
|
|
|
CURA-7413
|
|
|
|
|
|
|
|
Previously, the ironing_inset was changed in the profiles to reflect
the changes made in the CuraEngine. This inset though was not taking
into account the ironing_pattern (in the CuraEngine, the inset is
compensated differently depending on the pattern).
This commit fixes that in the version upgrader and the printer
definitions in order to maintain the same behavior for the old
profiles.
CURA-7318
|
|
Unify pause at height scripts
|
|
the same
The slicer has been adjusted to give this setting a more logical function: It should be an inset of the outer edge of ironing as it appears in layer view where the lines are made thinner according to their flow.
As a result all of the slices with ironing have changed. This adjusts the setting value so that the actual slice output will not change, just the appearance of the setting.
Contributes to issue CURA-7318.
|
|
These have a slightly different syntax apparently.
I thought I tested this before. But apparently not well enough.
Contributes to issue CURA-7433.
|
|
|
|
Contributes to issue CURA-7433.
|
|
No idea why it worked on ghostkeepers' system. It isn't supposed to: https://bugs.python.org/issue16058
CURA-7433
|
|
CURA-7433
|
|
|
|
This was changed from a number of layers to just a boolean for 1 or 0 layers.
Contributes to issue CURA-7413.
|
|
As explained in the comment. We reverted a change in 4.6, so we must unrevert it in master again.
Contributes to issue CURA-7420.
|
|
Conflicts:
plugins/VersionUpgrade/VersionUpgrade460to462/VersionUpgrade460to462.py -> On master we removed the getCfgVersion function, while we moved the entire plug-in to a different folder in 4.6.
resources/definitions/skriware_2.def.json -> On master we merged a PR that changes more or less all settings, while on 4.6 we doubled the maximum deviation.
|
|
CURA-7421
|
|
CURA-7421
|
|
CURA-7421
|
|
CURA-7421
|
|
CURA-7421
|
|
Oops. Small oversight. This could lead to the preferences file being erased completely.
Found during work on Sentry issue CURA-NH.
|
|
The code was moved to uranium, so no need to test them in a plugin.
In some cases they were also testing a specific implementation artifact and not
actual expected behavior.
CURA-7388
|
|
They can still be overridden, but in the current situation they were
all the same...
|
|
CURA-7383
|
|
American is Ultimaker's code style too.
|