Cura strips indents from conditional G code

OwenD

Just a heads up for anyone playing with conditional g code.
Cura strips leading spaces and tab indents from the start & end G code when you close the program.
So it’ll work fine when you test it, but next time you open Cura all the indents will be gone, so all commands will be executed.
e.g the example of

if !move.axes[0].homed || !move.axes[1].homed || !move.axes[2].homed
       G28
// rest of start code

will become after restarting Cura

if !move.axes[0].homed || !move.axes[1].homed || !move.axes[2].homed
G28

Causing G28 to be called regardless of how the IF statement evaluates.

Veti

move the code to a macro and call the macro

Phaedrux

This is a good case for using the start.g macro which runs when a print is started before any of the sliced gcode file is executed.

zapta

@OwenD, this justified a bug report or feature request (e.g. hard space) from Cura. Saving operation modifying the settings is bad.

OwenD

@OwenD

Oops. Forgot HTML would strip the spaces as well.
It was late. LOL

Yes you can easily use a macro.
Just remember that if the slicers doesn’t see some settings in the start code, it will automatically add them, so you may still not get the results you planned.

It’s going to take a while for the slicers you align with the new features.
As I said, just a heads up.