mirror of
https://github.com/Ultimaker/Cura.git
synced 2025-07-24 07:03:56 -06:00
Resolve is now updated from the base property
The resolve doesn't update always update well for single extrusion machines, so the wrong value gets used. There is however, no need for a resolve with a single extrusion machine, so we can disable the resolve for those alltogether. CURA-2939
This commit is contained in:
parent
6dc194d8de
commit
9057174691
4 changed files with 8 additions and 7 deletions
|
@ -114,11 +114,11 @@ SettingItem
|
|||
// 3: material -> user changed material in materialspage
|
||||
// 4: variant
|
||||
// 5: machine
|
||||
if ((propertyProvider.properties.resolve != "None" && propertyProvider.properties.resolve) && (stackLevel != 0) && (stackLevel != 1)) {
|
||||
if ((base.resolve != "None" && base.resolve) && (stackLevel != 0) && (stackLevel != 1)) {
|
||||
// We have a resolve function. Indicates that the setting is not settable per extruder and that
|
||||
// we have to choose between the resolved value (default) and the global value
|
||||
// (if user has explicitly set this).
|
||||
return propertyProvider.properties.resolve;
|
||||
return base.resolve;
|
||||
} else {
|
||||
return propertyProvider.properties.value;
|
||||
}
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue