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.
As the Limited will always apply on top of the others, so selecting the Distributed is
essentially the same as selecting the LimitedDistributed.
CURA-7555
As it will be applied by default in the Engine to ensure that libArachne will generate only the
required walls (based on the Wall Line Count setting).
CURA-7555
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.
