Exactly. Doesn’t look like they ever addressed it.
I have set my safety height to 1" before and all it did was cause the bit to go up 1" between travels during the carve. As soon as the carve was over it was right back to skimming over the work back to 0,0.
It was an early thing I noticed: manual generated g-code example
So apparently as I assumed in that thread, the return to 0,0 is hard coded and doesn’t read the safety height variable at all.
I really don’t want to have to use a different g-code sender. As far as I am concerned Easel is “integral” to the X-carve.
It has got to be just a few lines of code that for whatever reason are not getting the safety height from the variable that can be changed by the user.