Welcome to mirror list, hosted at ThFree Co, Russian Federation.

github.com/Ultimaker/Cura.git - Unnamed repository; edit this file 'description' to name the repository.
summaryrefslogtreecommitdiff
AgeCommit message (Collapse)Author
2021-10-20Merge branch 'master' into merge_main_20211019Remco Burema
2021-09-29Fix combing value not being recognizedKonstantinos Karmas
The value of an enum needs to be in single quotes when it is in the "value" field or else it won't be recognized. CURA-7976
2021-09-28Remove "default_value" since the "value" overrides itKonstantinos Karmas
CURA-7976
2021-08-06Also remove not-existing-anymore settings from definitions and the like.Remco Burema
CURA-7279
2021-06-18Perform version upgrade on newer profilesGhostkeeper
Should've done this in the merge, but I just increased the setting_version for these. I also removed a deleted setting from the advanced visibility. We don't have tests that ensure that these visibility presets are good. Lucky I found it then, with a Ctrl+Shift+F search.
2021-02-22def.json updateLukkoz
2021-02-22skriware 2 print settings updateLukkoz
profiles for skriware 2 added, def.json updated, some resolve problems fixed.
2020-06-30skin_outline_count default_value changed to valuejelle Spijker
Since the top container defines a default_value and a value Part of CURA-6684
2020-05-20Correctly upgrade the ironing_inset based on the ironing_pattern usedKostas Karmas
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
2020-05-18Adjust the default values for ironing_inset so that the slice result remains ↵Ghostkeeper
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.
2020-05-08Apply version upgrade maximum deviation change to built-in profilesGhostkeeper
For some this is not exactly restored as their original since this setting is limited to micron precision as well. Contributes to issue CURA-7420.
2020-04-30Merge branch 'master' of github.com:Ultimaker/Cura into 3mf_platform_meshesJaime van Kessel
2020-04-28Remove old 'category' metadataGhostkeeper
Most of it was incorrect and very inconsistent too. These are not used by our code any more.
2020-04-21Merge branch 'master' into 3mf_platform_meshesGhostkeeper
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.
2020-04-20Ensure consistant spacingJaime van Kessel
2020-04-18Replace STL meshes with 3MF filesGhostkeeper
These are much smaller than their STL counterparts. This saves on download and installation time. Maybe also on loading time.
2020-04-17Removed unnecessary parameters.skriDude
2020-04-10Changed selected "default_value" to "value"skriDude
2020-04-09Update in print qualityskriDude
2020-04-01Halve the defaults in Cura's built-in profile for maximum deviation tooGhostkeeper
Apply the version upgrade to these profiles too, essentially. Contributes to issue CURA-7282.
2020-03-24Adjust wall thickness to 1 line if using spiraliseGhostkeeper
Except for printers that explicitly override it. Fixes #7317.
2020-02-27Use spaces instead of tabsGhostkeeper
And remove floating point rounding errors too. Contributes to issue CURA-7260.
2020-02-27Merge branch 'master' of https://github.com/skriDude/Cura into skriDude-masterGhostkeeper
Conflicts: resources/definitions/skriware_2.def.json -> On master the old setting value was changed to 'value' rather than 'default_value', while on this branch the value was changed to use the resolve function.
2020-02-20fixed support layer heightskriDude
2019-12-23Fix identationJaime van Kessel
2019-12-23Remove removed settingJaime van Kessel
2019-11-04Fix zigzag initial layer pattern for Skriware 2Ghostkeeper
2019-11-04Fix complaints from CI system about settings that don't workGhostkeeper
There's one that needed to be a 'value' to properly overwrite it. The rest are all about settings that were equal to the defaults anyway so I've removed those. Contributes to issue CURA-6949.
2019-11-04Changed "values" to stringsskriDude
2019-11-04Changed selected parameters "default_value" to "value"skriDude
2019-10-30updated machine_start_gcodeskriDude
2019-10-21add skriware_2.def.jsonskriDude