The top/bottom speed is reduced by 80% to allow for better cooling of the top layers. This reduces pillowing. The line width is increased by 80% to maintain the flow equalization. PP-95
These images are binary data, usually quite big and change often. We don't want to make the Git checkout unnecessarily huge with this. We'll put those properly in cura-binary-data.
The HTML files are not really binary, but they belong together so it's easy to administer them if they are in the same repository.
It is a global setting, so it can't currently be changed with an intent profile.
A resolve function would resolve this. But which function that should be is to be decided.
Contributes to issue CURA-8746.
Our FastConfigParser doesn't deal with these safely. It's best to disallow comments altogether. They affect the line afterwards.
Contributes to issue CURA-8746.
This is more in line with what you see, so you can click on the icon properly to open the per-object settings panel. And the text gets properly elided where the icon starts.
And an example of such usage: In the material sync via cloud we only want to sync with printers that can receive those materials.
We might want to add a message for the user to also make sure the firmware is up to date. Because if the firmware is not up to date now it will show no printers and instruct the user how to connect the printer to the cloud.
Contributes to issue CURA-8671.
We changed tree support to have a correct top distance now. If you ask for 0 top distance, you get 0 top distance. If you ask for 0.2mm top distance, you get 0.2mm top distance (rounded to layers). Previously the top distance was too high. Yet it seems that people were happy with how easily Tree Support was removed from the print. So this is a best-effort attempt to keep the final result similar to what it was originally.
It won't work for everything, I fear. But it's about as good as we can make it.
Contributes to issue CURA-7624.
The engine would reserve space for each outline that should be there according to the count, not for each wall that was actually printed. Values of 999999 where chosen after discussion for _some_ of these (but not anything to do wit hskirt-brim, since we use those in the frontend for dissalowed areas) becasue then you can just fill a number of nines to get a completely 'walled' model printed.
We removed the limit of density for the first bridging layer, but there are more settings for that, and there's a similar arbitrary limit for flow in place.
Contributes to issue CURA-8639 and #10736.
