hazzy - Another touchscreen GUI

I think showing joints in FREE mode should be determined by the ini file, if non trivkins then show joints, if trivkins with kinstype=BOTH then show joints, if plain trivkins then no need to show joints.
Similarly with home buttons, if the joint has a HOME_SEQUENCE in the ini file it has no need of an individual home button but if it doesn't have a HOME_SEQUENCE then it needs an individual home button.

Cheers, Phill

Rod, you make a good point there. I guess the only reason to have individual homing buttons would be if the homing sequence is not defined in the INI file, or, maybe, for something like a SCARA robot. Axis and Gmoccapy have individual homing buttons, but come to think of it, I only use them but once in a blue moon.

If there are going to be joint pos DROs, I would think it should display all the joint present in the machine. But most users probably never will care about the joint positions, so maybe I should make the joint display optional (or just play hidden) if the machine has trivial kinematics.

Pedro, I am glad to hear you got hazzy to run! There are a lot of things that are not functional yet (especial on the file chooser page), but hopefully you can get a feel for what I am trying to do.

Thanks for the input all!
Kurt

Phill, I guess you type faster then I do
I think what you describe is an excellent solution as it would work in all cases, and should make everybody happy. It should also be quite easy to implement. Thank you!

Kurt

kcj wrote: Phill, I guess you type faster then I do
I think what you describe is an excellent solution as it would work in all cases, and should make everybody happy. It should also be quite easy to implement. Thank you!

Kurt

I agree too. For the record, I never even knew world/joint mode existed until Norbert started asking me questions in relation to the bugs I came up against!

Lets face it, its only something of interest to integrators like us on the forum, the average user won't even want to know about joints!

rodw wrote:

kcj wrote: Phill, I guess you type faster then I do
I think what you describe is an excellent solution as it would work in all cases, and should make everybody happy. It should also be quite easy to implement. Thank you!

Kurt

I agree too. For the record, I never even knew world/joint mode existed until Norbert started asking me questions in relation to the bugs I came up against!

Lets face it, its only something of interest to integrators like us on the forum, the average user won't even want to know about joints!

Unless they are using ja with a gantry machine. Thats the first thing that pops up when starting linuxcnc

Hallo,

rodw is right, I solved the gmoccapy gantry homing issue. I also need a correct INI config, but I do check within getiniinfo the kins and some more stuff, to display the DRO or JOINTS Pos.

Take care, that till now the jogging problem is not solved. The user of a gantry is still able to jog one joint without homing the machine, I am working on that!

Norbert