Age | Commit message (Collapse) | Author |
|
This alias shouldn't be written any more since the firmware misinterprets the setting value and errors when it's more than 100%.
Contributes to issue CURA-7724.
|
|
The function in the parent class has changed its type in commit 7968fe6d56205b20be9ba47e5a19be9f5914b084. This one should also change type.
|
|
|
|
|
|
|
|
CURA-6255
|
|
Previous solution was more defensive but also introduced dependencies
and extra files for minor benefit
CURA-6255
|
|
CURA-6255
|
|
Conflicts:
cura/Machines/MaterialNode.py -> Due to some automated formatting tool. Please disable those tools, people.
|
|
part of CURA-7041
|
|
These settings are currently unused by cura, but passed into the PPA
output. Some considerations:
- material_ prepended to all. Even though they are not all
material specific. The consistency is more developer-friendly imho
- defaults taken from generic_pla
- type is float for all, consistent with what I found in this file
CURA-7041
|
|
part of CURA-6971
(cherry picked from commit 25f0460231fd970b73744fb3fe1c004dc68a5dc9)
|
|
part of CURA-6971
|
|
part of CURA-6856
|
|
part CURA-6856
|
|
part of CURA-6856
|
|
Needed to add the filename to deserialize, feels a bit unsafe as an optional parameter, will discuss tomorrow.
part of CURA-6856
|
|
CURA-6920
|
|
CURA-6868
|
|
The material groups are not filled any more in the material manager so this fails.
This might make updating metadata of material profiles slightly slower, but when testing this I noticed no difference.
The function becomes a lot simpler though. And it works again.
Contributes to issue CURA-6600.
|
|
|
|
|
|
Since they didn't access any class attributes, there is no need for them to be classMethods
|
|
|
|
|
|
Oops. This is simpler anyway.
Contributes to issue CURA-6600.
|
|
Contributes to issue CURA-6600.
|
|
Otherwise we'll encounter that the variant name is None when serialising that subprofile.
Contributes to issue CURA-6600.
|
|
Material profiles need to serialise subprofiles that belong to different printers as well. Some of these materials may not be loaded in the ContainerTree structure. To prevent having to load that as well, we're just not going to use the container tree any more. It turns out that the only reason it was using the container tree was to get the hardware_type metadata from the node in the tree. So just get that from the container itself and we're fine.
Contributes to issue CURA-6600.
|
|
Not the variant manager, because it's deprecated.
Contributes to issue CURA-6600.
|
|
CURA-6600
|
|
part of CURA-6600
|
|
Conflicts:
.gitlab-ci.yml
cura/Machines/MaterialManager.py
cura/Machines/VariantManager.py
cura/Settings/ContainerManager.py
cura/Settings/MachineManager.py
tests/TestMachineManager.py
|
|
So now we no longer make material subprofiles per buildplate.
And now we create subprofiles for variants regardless if the variant exists or not.
Contributes to issue CURA-6600.
|
|
This mostly just makes it easier for me to debug where the manager is obtained from the deprecated singleton signal.
Contributes to issue CURA-6600.
|
|
They were caused by upgrading to a higher mypy version, which found more mistakes
|
|
Contributes to issue CURA-6672.
|
|
CURA-6672
|
|
Change to align with the name in the XML material files.
Contributes to CURA-6662.
|
|
These have been renamed for greater clarity. We also have to rename them on this side now.
Contributes to issue CURA-6329.
|
|
|
|
CURA-6590
|
|
This setting is no longer used. If I don't remove it, it'll complain when syncing materials with the printer because it tries to serialise the material profiles then.
Contributes to issue CURA-6329.
|
|
These need to be read for the deprime experiments in the PPA.
Contributes to issue CURA-6329.
|
|
CURA-6156
|
|
It is already serialised in the 'hardware compatible' settings.
|
|
This is both faster and actually functions properly.
Contributes to issue CURA-6272.
|
|
|
|
|
|
CURA-5787
|