There were a number of problems with it:
* There were duplicate JSON keys. One of the duplicates gets ignored then according to the JSON implementation in Python.
* There were some 'value' properties that contained undefined variables since the setting type was a string and the value is a string containing a Python expression that should result in a string, not a plain string.
* There was one instance in which a 'default_value' property contained a formula.
Contributes to issue CURA-7752.
* Added BIQU machine base files as well as BIQU B1 machine files.
* Fixed a variants settings version error.
* Updated base def by removing excluded materials and changing the pref to pla175
* Fixed the machine name value which should only take a default value and not also a value.
* Increased the max extruder feedrate to allow the default retraction speed.
* Removed comments from the quality profiles. Removed author from variants. Adjusted materials in quality profiles to refer to the 175 profiles directly.
* Enabled coasting by default in the B1 profile and increased the width of infill for the base profile.
* Updated all quality and variants configs to use settings version 16 in anticipation of release 4.8
* Final tweaks to B1 start gcode
* Added an ABL version of the B1 with tweaked start codes.
Can keep the CPUoccupied for a long time with higher values. Decided that very few people will need that many layers anyway. Rather than complete defer, at least warn people something might be up.
a 5-min. fix
* Add Creality CR-6 SE definition
Also did a few changes in the creality base.
* Add Creality CR-6 SE Nozzle variants
* Update creality_base.def.json
Reverted back to the 4.7 base file
* Update creality_cr6se.def.json
* Update creality_cr6se_0.8.inst.cfg
* Update creality_cr6se_0.6.inst.cfg
Updated to version 16
* Updated to version 16
* Updated to version 16
* Update to version 16
* Update to version 16
* Update to version 16
* Add files via upload
* Add files via upload
* Add files via upload
* Update fusedform_300_draft_abs.inst.cfg
* Add files via upload
* Delete fusedform_300_draft_abs.inst.cfg
* Delete fusedform_300_draft_pla.inst.cfg
* Deletion of old files
* changes in STD quality profiles
* Changes in mini quality files
* Changes in FF600 quality files
* changes in machine definition name
* Changes in definition files
* extruder and definition linking
* ff300 inherits and extruder def
* Update fusedform_300.def.json
* category deprecation in definitions
* inherits
* ff300 extruder definition machine
* extruder machine definitions
* Fused form FF600plus machine profiles
* PETG profiles
* Update fusedform_300.def.json
* changes in start gcode
* machine configuration dynamics on definitions
* speed adjustments
* dynamics modification in petg and flex quality
* Further adjustments on dynamics definitiosn
* Modification of all files under inherits data structure.
* Quality setting version 15 to 16
* These changes are for limiting quality types in the materials defined
* Quality Modification under Global and Material specific structure
Global quality structures and material specific definitions under the global structures
Since the prime tower for other extruders is now folded into one instead of alternating the layers, you need to have enough diameter to print all extruders, not just the current extruder.
Fixes one side-issue mentioned in #8148.
A small positive (>100) value is correct. It needs to compensate by increasing the size, usually. If you need to compensate by making it smaller, that means that the material would expand when cooling, which is very rare.
Contributes to issue CURA-7118.
We have a change now that requires a version upgrade. This triggers all profiles to update for the user, and we must update accordingly in the built-in profiles.
Contributes to issue CURA-7118.
We'll now actually compensate for the shrinkage. That means that the setting needs to become user-visible. We need to make that experience a bit more user-friendly.
The setting is now also global, with a resolve function. That means that the user can't change this per extruder any more, because the scale factor applied in the engine can only be global. The resolve function means that profiles can still apply a per-extruder value but this value gets resolved with other extruders' values.
Contributes to issue CURA-7118.
This reverts commit 28f4d8513db7efce17bfd8b80fa7c8b237fd1c18.
The original revert was to revert an accidental merge from master to 4.7. This now reverts the revert on Master, so that we still have those changes on Master.
Previously this was disabled because you should probably use the ZigZag pattern then. But I'm enabling it now because of two inconsistencies:
* The setting still works. So you can change the setting by switching to grid, triangles, cross or gyroid, then switch back to lines and still get connected support lines.
* The same happens with the infill patterns, where this setting is visible for the lines pattern.
Rather than changing the other two things (which involves changes to CuraEngine too to make it ignore the setting value for the lines pattern), I've opted to change it here and fix both inconsistencies at once. If I were to make the setting dysfunctional, it would also lead to user confusion, because they then need to discover that they need to change the infill pattern, which may look unlogical to them.
Fixes#8192.
This was decided on by the material & process engineers. It's a pretty safe change since the support brim pretty much has only advantages if there is no support infill.
Fixes ST-3552.
I think for the support meshes, some settings were simply missed because they are in completely different categories. For instance, the support flow rate also applies to support meshes so those settings should be visible.
For the tree support settings, I think that when the tree support became activated by support_structure, the developer checked for instances where the support_tree_enable setting made a setting visible (as alternative to the normal support_enable setting). Like Support Infill Density used to be visible if normal support or tree support was enabled, and now needs to check only for normal support. However they didn't also look for settings that are ONLY available for normal support and not for tree support. So those settings now have extra conditions that disable them if the support structure is set to tree support.
With this I tried to word the check correctly in case we ever get a third support construction type. Like, sometimes a setting is not shown with tree support because tree support explicitly doesn't support it (e.g. Conical Support), but sometimes it's not shown with tree support because it's specific to area support (e.g. support join distance).
Done as a five minute fix (although typing this commit message also took five minutes) as I encountered these problems while working on the settings guide.
That was still missing, oops. I'm aborting the translations to get this in. It's important enough to break the string freeze and restart the translations process at this stage.
Contributes to issue CURA-7622.
Some printers stylize themselves with allcaps to gain more attention or because they use fonts that don't have lowercase (especially Asian brands) or to mix it with fixed-width characters. Here we'd like to keep them all equal, so they get proper name-style capitalisation.
