Otherwise you get layers where the prime tower isn't printed because it is less than twice the line width, and then the prime tower falls away. I'm sure this was the whole intent of this 'max()' clause but it was executed wrongly.
Now that users have gradual infill available as option in recommended mode, it was deemed better to let the user choose when he wants it. I left the step height intact, in case the user chooses it anyway.
If it's less, the layer doesn't get properly filled, according to the materials team. They requested that the thickness should be set to 0.225mm for just the Fine and Extra Fine profiles, but I opted for a formula that would still let it scale with the layer height up to a point.
These are the translations we got from Bothof. They are unabridged, no edits are made. They are not checked yet. I'm going to do that afterwards.
Contributes to issue CURA-3885.
CURA-3884
We rely on the machine to decide whether it needs machine specific
materials, so we don't override the filter_by_material flag when
looking for quality profiles for a material.
Even though it was commented-out, it was still being detected and made Cura think that the start g-code was heating up the nozzles by itself. I've removed the lines so that the normal temperature commands get inserted by Cura automatically.
Because of the missing files for fdmextruder and fdmprinter, I re-generated these translations from the POT template. But that erased them, so I put the old translations back and then updated them properly with the new keys.
Contributes to issues CURA-3885 and CURA-3817.
These were generated using 'make i18n-update-po' on the 2.6 branch at commit 37fccecce7e5f81d3b5bf70ad981602c97120669. This should add all new strings to all .po files for Cura and retain any old translations that we had.
Contributes to issue CURA-3885.
CURA-3881
CuraContainerRegistry._activeMaterialId() can return an empty string
if there is no active material, and in this case, importing a custom
quality file will fail.
CURA-3738
Getting limit_to_extruder from definition in QML returns a
SettingFunction which hasn't been evaluated. This causes the comparison
not to be working. We change it to use the global stack to evaluate so
we can get an actual extruder number string.
