LinuxCNC Features - a kind of NGCGUI

Hi Martin

About "my variable names are short ENA" , keep PARAM_ENA and all PARAMS short but give them a significant name like "Enable" that will display in the tree. A line of code must be <256 characters but the display is not limited

About Inkscape, I agree it is not really fun to learn a new app just for an icon. But if you want to try it, open icons.sgv, select one icon then ungroup to see all the components they are made of. And yes it is not at all like GIMP. I made a few but I still need some. What is interesting by copying and editing is they match with the others. I hope some day someone else is willing to create more.

About 'cutting-params and diameter', look at my screenshot showing all kind of lines, the top one. Far right is a rectangle where I set tool diameter compensation. The outside line are what the final cut will leave and the inner lines are the tool path. Same for the circle (far left) which is based on helix. So when I want a rectangle 10X20, this is the size I set, I do not have to calculate tool diameter. I agree that code is written once but what is interesting with tool compensation is that it will follow any line correctly. You have to do the tool change first.

I do not have a tool changer and am writing code for using my probe to reset Z position like in those videos




and my probe is this one
www.micro-machine-shop.com/3D_digitizing.htm

110 USD from
wildhorse-innovations.com/index.php?_a=viewProd&productId=80

I will look to modify the code to use same "menu.xml" for menu or icon view interface

Regards
Fern

Hi Martin,

I was able to load your menu with minimal changes to it, but unable to load any ini, because I think it is because your folders structure is more complex than mine. Also, when loading the icons, it was the large image that loaded. First see what needed to be changed in the variables to set the path and what it looks like when loaded. Subfolders are possible in all path, it then depends of the ini







And writing code to change tools any number of times in a job and use the probe to compensate for length is a complete success

Regards
Fern

Hi Fern,

sorry fo no reaction from my side...

In the moment I have to fight with another piece of software (BLDC-controller),
that must be finished on Monday.

Hopefully I have some time to go through all the posts during the weekend.

best regards,

Martin.

Hi Nick

It is possible to use larger icons in the menu like this




OR

combine menu AND iconview like this



It is just a matter of selecting True or False in features.py

What do you think ?

Best regards
Fern

Hi,

I would like some feedback on this one

The top treeview shows the structure of the job, while the bottom one shows the params of the selected one

Tell me if you think it is a good or bad idea



Regards
Fern

Hi Fern,

...I finished my other software job, so I hopefully have some time now for this project...

Your menue looks great. For me it is a better solution than the original one.
But I am using a mouse. not a touchscreen. I think, the original one is better
for touch screens. So can we have both? Selectable vie commandline parameter?

Your windows with the two treeviews is also a good idea.
The only problem I see there is, that on low resolution screens, the height of the
display may be too small to use it. Can the bottom treeview part be moved
right of the top one (also switchable via commandline parameter or config file)?

One thing we should discuss is my work on the subroutines folder:

Have you had success in using it in your menue structure?
There was one post saying, only the top level is working.

One thing I would like to know is, if anyone else would like to work with
my subroutines. The problem I see is, that I have modified many things
on the parameters ( inside cutting-params and new-params, the
parameter names etc...)

Would it be a good idea to mix my subroutines with the ones made by Nick?
I think, the we have to adjust Nick's subroutines to my parameter names.

Or should we have two separate "subroutines folders"?

Or should I keep my one private?

I think, Nick's subroutines cover most of all things needed.
My subroutines are a bit special...
And maybe only working good on my machines.

So I would like to have an opinion what to do and how to continue.

If we mix the things together, then it would be usefull to add my subroutines
to the source tree made by Nick on github. Having a separate subroutines
distribution would make things more complicated in my opinion.

best regards,

Martin.