Gmoccapy - A new screen for linuxcnc

Hi Norbert,
there is a small problem autoscale of custom panels:

solved (right figure) by adding in gmoccapy.glade for custom box (box_custom_2 in my case) but I should not touch gmoccapy.glade.
How best to resolve it?
Whether GTK+ allows access to the property of the parent from the dynamically connected child ?

Halo Verser,

as I did not find any side effects of your changes, I made them standard and just pushed the corrections.
It will work as you wished from ver. 1.0.6.2 (actual from now on)

Norbert

Addition Compensation Z is ready.
Norbert, thanks for the help
cnc-club.ru/forum/download/file.php?id=25699

I needed to give my mill a spin a few days ago so i decided i could as well try the latest and greatest gmoccapy.
Transition from 0.9.9.9.(...) to 1.x version went suprisingly smoothly. After reading about other users' problems i was prepared to spend half an hour or so tweaking configs and persuading git to pull the new version, but it was only a matter of doing git pull, make and changing names of two hal pinsnftom gscreen.* to gmoccapy.*

Everything works great, no new problems to report so far. Being able to double click files and folders to open them saves some time and frustration
Great job as always, Norbert.

As for z compensation i was planing to try it out for some time now. Not having to mill a flat bed for pcb should save some time and allow for simpler mounting. Thanks for implementing it right in gmoccapy, verser. I'll have to give it a try with the next pcb i make.

Thanks for the compliment :woohoo:

gmoccapy now is 1.0.7.1

- when a external ESTOP was active and the tbtn_estop has been clicked
it changed its color, but should not do so, solved
- when external estop was active, it was possible to click the on button
and the GUI changed state making several widgets sensitive, that behavior
was wrong, solved that.
- If you feed override has been changed and the machine went into estop,
a estop reset also reseted feed override to 100 % , now it will remain with
the value it had before estop.
- If a user activate logging actions, the logging was lost after shutting
down the GUI, now the content of alarm_history will be written to a
file called gmoccapy.log in your config dir. The file will be overwritten
on each shutdown of gmoccapy with the new content.
- EXIT Button is now only sensitive, when machine is switched off, so it is
not longer possible to accidentally shut down the machine.
- pressing estop from MDI mode with spindle on, resulted in an error, solved.

And the changes of previous versions:
ver. 1.0.7
- Reworked the emergency button behavior as well as the
on/off button, as it was possible to set the GUI in an ESTOP_RESET
state, even if an external SWITCH was in ESTOP State. The important
bug has been found by Steffen, he also supplied the initial patch,
witch has been adapted to my coding style
- Next changed the error handling, separated the error reporting from
periodic to an own function, so we are able to launch also our own
errors over the same channel, and get error pin height and also
the sound will be played.
- Deleted some unneeded or dobble code.

ver. 1.0.6.3
- Bug turning on flood with M8 and logging actions on,
found by Stephen, solved that one

Please do not find more bugs I would like to go on with luminos.

Norbert