mirror of
https://github.com/Ultimaker/Cura.git
synced 2025-07-06 22:47:29 -06:00
Keep current_e updated even if not finding retractions
Otherwise the new E is never going to be lower than the current E. I don't know how this ever worked then. Contributes to issue CURA-7351.
This commit is contained in:
parent
d9649dc3dd
commit
9b997d421b
1 changed files with 1 additions and 0 deletions
|
@ -42,6 +42,7 @@ class RetractContinue(Script):
|
||||||
continue
|
continue
|
||||||
new_e = self.getValue(line, "E")
|
new_e = self.getValue(line, "E")
|
||||||
if new_e >= current_e: # Not a retraction.
|
if new_e >= current_e: # Not a retraction.
|
||||||
|
current_e = new_e
|
||||||
continue
|
continue
|
||||||
# A retracted travel move may consist of multiple commands, due to combing.
|
# A retracted travel move may consist of multiple commands, due to combing.
|
||||||
# This continues retracting over all of these moves and only unretracts at the end.
|
# This continues retracting over all of these moves and only unretracts at the end.
|
||||||
|
|
Loading…
Add table
Add a link
Reference in a new issue