aboutsummaryrefslogtreecommitdiffstats
path: root/docs/Config_Changes.md
diff options
context:
space:
mode:
authorKevin O'Connor <kevin@koconnor.net>2019-05-20 22:36:57 -0400
committerKevin O'Connor <kevin@koconnor.net>2019-05-26 11:19:15 -0400
commitd6b69938abcff61ca1c2323899ec74eac149f13b (patch)
tree55db94cd411d52172e4c096732c3320015e8b6d8 /docs/Config_Changes.md
parent500f37821dd0ceeac2ce2636093565e987c8ba40 (diff)
downloadkutter-d6b69938abcff61ca1c2323899ec74eac149f13b.tar.gz
kutter-d6b69938abcff61ca1c2323899ec74eac149f13b.tar.xz
kutter-d6b69938abcff61ca1c2323899ec74eac149f13b.zip
gcode: Don't apply the SET_GCODE_OFFSET to the next g-code command
The SET_GCODE_OFFSET command could cause unwanted behavior when an offset is applied to the following g-code command. (In particular, when the following command is an extrude only move - as in issue #1289.) Don't apply the offset immediately. Instead, add support for a MOVE=1 parameter which will schedule a move to apply the given offset. Signed-off-by: Kevin O'Connor <kevin@koconnor.net>
Diffstat (limited to 'docs/Config_Changes.md')
-rw-r--r--docs/Config_Changes.md5
1 files changed, 5 insertions, 0 deletions
diff --git a/docs/Config_Changes.md b/docs/Config_Changes.md
index f7e8017d..7ce25a1b 100644
--- a/docs/Config_Changes.md
+++ b/docs/Config_Changes.md
@@ -6,6 +6,11 @@ All dates in this document are approximate.
# Changes
+20190520: The SET_GCODE_OFFSET command has changed; update any g-code
+macros accordingly. The command will no longer apply the requested
+offset to the next G1 command. The old behavior may be approximated by
+using the new "MOVE=1" parameter.
+
20190404: The Python host software packages were updated. Users will
need to rerun the ~/klipper/scripts/install-octopi.sh script (or
otherwise upgrade the python dependencies if not using a standard