Generic Probing tab

Quadro wrote:

would it be best to call ngc file subroutines for each probe event instead of embedding it into the software.

That wasn't the game I was playing. I was trying to see if it was possible to keep the whole thing as one file. I was disappointed when I found that I needed two, one for the python and one for the graphics.

The normal way would be to have a Python handler file, a graphics file and an ngc file for every button, all linked by a Glade file. I wanted to avoid that level of "clutter" and the associated scope for files to not be found.

(Incidentally, in MacOS this would be less of a concern as executables are "bundles' that can contain all the resource files they need)

It is trivial to create a set of buttons that call ngc subs in Glade. I was playing about with something that seemed more interesting.

newbynobi wrote:

So add a parameter to the call, as --use-extern-files and switch that way from your internal code to user code.

It isn't actually any harder to edit G-code embedded in a Python file than it is to edit G-code in any other file. As Python is interpreted the changes take effect just as easily.

Neverthereless i like the way linuxcnc features is handling this. It is quiet easy to modify the on board code, just editing some ini files. Have you taken a look at the code?

Not yet, I am a long way from a LinuxCNC machine at the moment.