The material team observed that the size of prints was slightly too big. They decided that this adjustment was the best solution.
Contributes to issue CURA-2845.
I've made sure that the behaviour of getAllExtruderValues remains the same, so that this function may still be used by other pieces of code. It is now just a special case of getAllExtruderSettings. Please suggest a better naming scheme, if you like.
Contributes to issue CURA-2823.
The carot indicates start of string, the dollar the end of string. So it must match on the entire string, not a piece of it.
Contributes to issue CURA-2692.
There is also a more advanced attempt that allows more, but I've commented it out because it doesn't quite work yet. Special characters now always count for 12.
Contributes to issue CURA-2652.
Currently this validator can't be used in QML due to a PyQt bug. I plan to call the validator manually upon receiving a signal that the text changed in a text box.
Contributes to issue CURA-2692.
Instead use the "compatible" metadata entry like we do for nozzles.
Setting the type differently caused all code that looks for materials to
fail because "incompatible_material" is not "material". Since this is
the base file, this meant a lot of materials failed to duplicate
properly which caused crashes.
Contributes to CURA-2821
We include these plug-ins with the build system, but for development it's easy to have them linked or copied into the plug-ins folder. But don't commit them! So here we ignore these plug-ins.
These are the latest fixes that will be included in 2.3.1. Not all of these are entirely complete yet as of this writing. These are only the fixes that are worth mentioning in a change log.
Contributes to issue CURA-2755.
This order is closer to what's on the website of Ultimaker, and more closely reflects the relative importance of these features. No 1:1 matching is possible with the website though.
Contributes to issue CURA-2755.
This is now updated with all that's on the website. In many cases, the wording of the Ultimaker website is also chosen, unless that wording was only to make it fit better within the style of that website.
Contributes to issue CURA-2755.
If there is no unit known, it is interpreted as there being no unit. There is currently mm, but if we changed that it is probably on purpose so we write no unit.
Contributes to issue CURA-2723.
The footprint of the function changed, but the call wasn't updated, apparently. I pulled new_name up from one of the if-statements since they need to be computed for both branches now (and they are the same).
Contributes to issue CURA-2785.
