Lathe Macros

About using oriuginal lathemacro.ui with the modified files is not a good idea.

About error message i think this is because the program does not found you macro folder

This is my config parts :

[DISPLAY]
EMBED_TAB_NAME = Macro
EMBED_TAB_COMMAND = gladevcp -u ./python/lathehandler.py -x {XID} ./lathemacro-en-numpad.ui

[RS274NGC]
SUBROUTINE_PATH = ~/nc_files:~/my_Lathe_and_Mill/nc_subroutines/lathemacros

Hi

I have start a github for expose new version of lathemacro
github.com/alkabal/Linuxcnc-LatheMacroV2

To Andypugh : if you dislike that for any reason feel free to ask for remove or if you wish to create a more official git this can be perfect

Br

alkabal wrote: I have start a github for expose new version of lathemacro
github.com/alkabal/LatheMacroV2

I have only got as far as looking at the top image in the SVG file.

It seems to require that the right-hand end of the work is zero. That is not the way that my macros work, and I see it as not an improvement.

All my macros begin at the current (jogged-to) tool position and finish at specified Z and X values.
This means that the workpiece origin can be anywhere on the part, which is rather more flexible than what you appear to have done.

If I was doing it again, I would probably try harder to generate the graphics live rather than use fixed images.
But I would definitely not use the overlaid table.
I did, in development, have a scheme whereby the numeric entry boxes were actively scaled in position as the image was resized. I think I should have stuck with that idea.

alkabal: As a general note. I am sorry that I don't spend as much time looking at your prolific work as you would like, but very nearly all my spare time is already taken up with other bits of LinuxCNC. I (and other developers) can be expected to answer clearly stated questions, but checking out a new feature and working out what it is meant to do takes time. And working out how to test / evaluate it takes more time. Time that we might not have.

Hi

I understand 100%, i ask for review but this is only if you (or toehr) like to do it off course !

For the live graphics parts unfortunately for now this is something not easy for me.

Regarding to 0 in front of worpieces this is juste some wrong information, this is not required to do the zero (code logic is unchanged) i can remove completely or better found the good word like "macro start position"

Thanks

I'm confused by the path config.

I previously had this path in my INI file:
SUBROUTINE_PATH = subroutines

I believe I need to add the lathe macros folder, which looks like this in my case. I suspect I can use an incremental(?) path but don't know how to implement that yet:
SUBROUTINE_PATH = /home/muzzer/linuxcnc/configs/probe_basic/probe_basic_lathe/lathe_macros_V3

How do I end up with both folders in my path? Do I simply separate them with a colon like this?
SUBROUTINE_PATH = subroutines: /home/muzzer/linuxcnc/configs/probe_basic/probe_basic_lathe/lathe_macros_V3

I'm a Linux noob as you can tell.

Also, the README file talks about .PNG files which seem to have been superseded by an SVG file. Presumably this has several images within it?

Yes, a colon separator should work.

There are two variants of the macros, a fixed-size one using PNG and then a resizable one using SVG (And, yes, all the images are different layers in the same file in the case of the SVG.)

The touchscreen / resizable version needs a button connected to the gladevcp "cycle-start" button to start each macro. I would encourage that to be a physical button.