Cura/cura/Machines
Jaime van Kessel 600cd7669c
Use the activeIntent from intentmanager instead of active stack
Otherwise the behavior of the model changes depending on what stack you
have active. I think that this was caused by some code duplication where one
copy of the code was updated but not the other one. This bug was here for quite
some time, but strangely enough, it was never found...

CURA-11854
2024-04-24 10:34:33 +02:00
..
Models Use the activeIntent from intentmanager instead of active stack 2024-04-24 10:34:33 +02:00
__init__.py WIP: Create VariantManager 2018-02-16 14:20:02 +01:00
ContainerNode.py Remove trailing whitespace from Python files 2020-05-29 14:30:33 +02:00
ContainerTree.py Add bit more logging around MachineNode loading 2020-07-20 16:03:06 +02:00
IntentNode.py Remove trailing whitespace from Python files 2020-05-29 14:30:33 +02:00
MachineErrorChecker.py Improve UI responsiveness 2024-03-18 13:24:52 +01:00
MachineNode.py Use camelCase for python function definition 2023-06-12 14:35:11 +02:00
MaterialGroup.py Remove trailing whitespace from Python files 2020-05-29 14:30:33 +02:00
MaterialNode.py Update MaterialNode initialization and metadata retrieval 2024-04-10 09:27:37 +02:00
QualityChangesGroup.py Search/replace Qt5->Qt6. 2021-12-28 14:46:02 +01:00
QualityGroup.py Remove trailing whitespace from Python files 2020-05-29 14:30:33 +02:00
QualityNode.py Remove trailing whitespace from Python files 2020-05-29 14:30:33 +02:00
VariantNode.py Update MaterialNode initialization and metadata retrieval 2024-04-10 09:27:37 +02:00
VariantType.py Move VariantType to VariantType.py 2018-08-02 16:11:55 +02:00