With limit_to_extruder, we always try to get the value of a setting from
an extruder. However, if the setting is not settable_per_extruder we
bypass the extruder and go directly to the global stack. This would
cause an infinite recursion.
Contributes to CURA-3738
* 'transparent_limit_to_extruder' of github.com:ultimaker/Cura:
Removed unused imports
Fixed type hinting for Extruder stack
Fixed two remaining failing unit tests
Fixes unit fallthrough unit test
The cause for this change is that TPU says we want to print with brim but CPE wants to print with raft.
In those cases the resolve function would choose the raft because that's safer.
However if the default extruder happens to be the TPU one you then get a raft made of TPU which is flexible.
That defeats the purpose of the raft, and causes the raft to warp, clog on the nozzle, destroy the world, etc. So there, I saved the world once more.
* 'master' of github.com:ultimaker/Cura: (94 commits)
Re-enable Japanese from language selection menu
Add Japanese translations for setting descriptions
Update PVA profiles
Changed profile names
Simplified some code
Changed final spot where we still used findContainer when looking for container with specific type
Directly use property instead of searching
Added a type hinting to QualityManager
JSON description fix: warn users when not to use spiralize (CURA-3636)
Add setting_version every time we create InstanceContainer
Increase warning value for gradual infill steps
Convert all metadata fields to string
cleanup: prime => prime blob and lil doc (CURA-3634)
fix: don't make disallowed area if blob is disabled (CURA-3634)
Be robust against older specification version numbers
Read setting_version from version attribute on root
Added bunch of typing to extruder manager
Fix resolve strategy "new" for user instance container
Added missing typehinting
Row element was not used
...
These updates bring different speeds for support-top vs. support-bottom, and changes the bottom pattern now that they are separately configurable. I also sorted the BB0.8 variant alphabetically (raft settings were out of place).
Except when we fill the instancecontainer via deserialising. Because then we want to retain the original version number.
Contributes to issue CURA-3427.
We set gradual infill steps to 5 if you choose Gradual Infill from recommended mode. This value was provided by the materials testers, so apparently it works fine and we shouldn't give a warning about that.
Contributes to issue CURA-3732.
1.2 and lower didn't specify a version number. Assume that it was 1.2. We feed this through our translation function for form, mostly, because we know that the setting_version should be 0 then.
Contributes to issue CURA-3427.
The fixture does this for us automatically now. It's not entirely neat since this is not cleaned up afterwards, but it does make sense to put it there in the fixture, logically.
Contributes to issue CURA-3427.
