From 9b997d421b25c1bfc56be7c68ba75fd8f6902653 Mon Sep 17 00:00:00 2001
From: Ghostkeeper <rubend@tutanota.com>
Date: Thu, 9 Apr 2020 11:22:05 +0200
Subject: [PATCH] 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.
---
 plugins/PostProcessingPlugin/scripts/RetractContinue.py | 1 +
 1 file changed, 1 insertion(+)

diff --git a/plugins/PostProcessingPlugin/scripts/RetractContinue.py b/plugins/PostProcessingPlugin/scripts/RetractContinue.py
index 315d8edf1a..aba55596b0 100644
--- a/plugins/PostProcessingPlugin/scripts/RetractContinue.py
+++ b/plugins/PostProcessingPlugin/scripts/RetractContinue.py
@@ -42,6 +42,7 @@ class RetractContinue(Script):
                         continue
                     new_e = self.getValue(line, "E")
                     if new_e >= current_e:  # Not a retraction.
+                        current_e = new_e
                         continue
                     # 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.