why not build a pilotpath like screen?

it seems lots of people like the pilotpath screen. Rather then try to unravel Tormach's code, why not just build a screen like it?
If the images are open source then one could even use them so it looks very similar.

There is infrastructure for building custom screen in linuxcnc called Gscreen. It's not easy but is doable.

I do wonder how Tormach would feel about this since the screen is really a selling point for them.

Chris M

They could perhaps argue that the 'look and feel' are proprietary/copyright even if the code isn't.
I certainly like the way it looks and the conversational side of things.

this is in hand , at the moment , however with over 100 images to construct , theirs a lot of work
this is also changing to incorporate new python and graphic api's. as seen in the newer debian distributions .

Do you mean you are building a complete reverse engineered screen?
You are not planning on using Gscreen ?

Chris M

I like PathPilot stability and features and i also like Gmoccapy clean interface and customizability.
I think we should focus to remove all the glitches and bugs instead of starting a new one

pathpilot is not in linuxcnc so hard to fix bugs on it.

Chris M

Chris, i mean do improvements and fixing the bugs in Gmoccapy/Linuxcnc

What bugs in gmoccapy you do refer to?
I think i fixed all known bugs!

Please report bugs, if you find some.

Norbert

Well I assumed that some people prefer the pilotpath style of screen over linuxcnc's other screens.
Other wise yes why build another.
Gmoccapy is bug fixed as soon as bugs are found, Norbert is very good about this.

there's a great and good work behind gmoccapy, i love it. Thank you Norbert.

I'm referring to some bugs/improvements needed to get gmoccapy rock solid and with all the functionalities like PathPilot.
Probably the most of behavior are not related to gmoccapy itself but linuxcnc/gtk/etc.

Now i'm not aware on the last development of it so i can miss something, but for what i remember my list is:

• macro not showing correctly in gcode listing
• when editing the offset table we can change only one field at time
• add the ROT parameter to be set in the offset table
• when using probe_screen the page is forced to switch back to mainpage, sometime not.
• Probe screen should be improved (i was working on it but i'm on hold now)
  
• Gremlin should be improved. It should not reset the view automatically
• Goto gcode line is ok? last time i tried no
• little improvement to M6 remap: when tool is on dont go to change position
• i've not tested features from a long time. But to complete the list the gmoccapy+feature+probe with all the jingle and bells would be great and i would like it more than PathPilot