Qtlathe

If you prefer text rather then images for the coolant status, that could be done too.

Some of the macros in the sample (ie got-to-home) are for mills, so have Y axis requirements that are not available in a lathe. New lathe only macros need to be made.

The lathe specific macros are based on Andy Pugh's lathe macro work.
But I do believe I didn't fully understand how they worked and they need to be fixed.
I also believe Andy's macro's required all data to be converted to metric equivalents.
I would prefer to have the displayed data to be displayed as either metric or imperial.

Macros that make plain gcode that could be freely edited after would be another desirable option.

More work to be done

Thanks for the reply. I added pictures, it’s good. I also added Gcode Edit but by default it does not load
file manager. After clicking the Edit button, everything is correct. Error saving file. What I did wrong? Please tell me. In the macro go-to-home, go-to-zero there is no Y, I removed it.
Gmoccapy_lathe_macros somehow work but for me it is not yet clear.

The problem is the tab split with filemanager and program editor together?
This will be something to do with widget switcher moving widgets around.

Originally the idea was the tab with the white border was active and then the external cyclestart button would work only on it. This was to roughly follow the HASS screeen.
It may make sense to rethink how the tab button call up tabs since you have changed it.

What is the problem with your changed macro programs?

I've been playing with a modified version of the nurbs editor to make a lathe facing editor that outputs plain gcode.
Not sure if it will lead to something useful:

Thank! I understand that the Prog button must be registered to open the file manager and close the Editor. Following the example code for the Edit button. But the biggest problem is that editor does not save the edited code. Error in the screenshot. Nurbs editor is very beautiful.

But the macro is what is in NURBS EDITOR. Lathe.ngc is not quite correct for an example.
I think that a turner will be able to create a macro for his tasks. INI - MACRO = lathe T Feedin/min Xin Zin SDin MRin SSob/min DOCin

Sorry I'm not following what you are saying.

Nurbs are not available on the Z plane, so nurbs editor is for Mills.

Macros are usually for one off actions.
The lathe editor widget would allow you to string together a full program.
The program would be plain gcode and fully editable / savable.
Or you could use it like a macro and just run it once and not save it.

Also the display allow you to see the program before running it.
I also allows one to build a program while another is running on the machine.

I'm just not sure I'm smart enough to build fancy turning-with-radius-ed-corner editor.

Chris

Let's leave the macro for now. Please tell me why the Gcode editor does not save
Editable Gcod?

It works for me. My guess is a translation problem.

in qt_action.py
under SAVE_PROGRAM
change to:

run linuxcnc from a terminal and look for ''**** save gcode filename'
and post the file name path here please.

Old age is not a joy. Does not save to the directory from which gcod is open. Saves unchanged action.py and with changes. It's a little uncomfortable. I changed the interface a little if you think you need to, add. Thank!