Conflicts:
resources/definitions/ultimaker2.def.json -> Additions in Arachne around a place where we fixed an enum setting.
resources/definitions/ultimaker3.def.json
resources/definitions/ultimaker_s3.def.json
resources/definitions/ultimaker_s5.def.json
This variable makes more sense to as a Ratio.
This was discussed during the eCCB 12/11/21
and implemented as a 5 min fix.
Note: The current default values were 0.5 there
is a new PR which change these 1.0. These values
should be multiplied with a 100
There is no theoretical or algorithmic limit here. We may warn the user, but not prevent them from changing it.
Done as a five minute fix. Fixes CURA-8693. Fixes#10736.
It doesn't work for those patterns at the moment. For Gyroid it could be made to work. For Cross and Cross 3D it's a bit more difficult due to the pre-calculations and density image done for those.
Contributes to issue PP-55. Done as a 5 minute fix.
These two have garnered some feedback in that it's wholly unclear what the sentences even mean. Hopefully this correction makes it more clear for next time.
Contributes to issue CURA-8638.
Two changes have been made:
- Use more consistent terminology for the top side of the model (which could be skin or walls). This is corrected from feedback by our translators.
- Don't add disclaimers about the infill density to this already way-too-long setting description. If anything, a disclaimer should be added to the infill density description that Gradual Infill and some infill patterns might not reach the desired density everywhere. But really, I think it's more in the domain of user documentation like the Ultimaker website or the Settings Guide.
Yes, it's my name. I'm okay with people learning that if they are really looking. I'm less okay with search engines learning that. Removing my name here linked to my nickname will eventually cause search engines to unlink it too.
This needs quotes, since it's a Python expression. Otherwise it would get interpreted as a variable name which doesn't exist.
Contributes to issue CURA-8627.
Otherwise the maximum gets ignored because the JSON results in a dict where the keys are unique. So the second one happens to get skipped then.
Contributes to issue CURA-8627.
This is interpreted as a Python function, so if it doesn't have those quotes it'll be interpreted as a variable name, and that variable doesn't exist.
Contributes to issue CURA-8627.
