Chris,
Your additions/modifications are working. I did notice that if I click on a button that has different text for "on" and "off" states that it requires a mouse button release before the text itself changes. So the text change cannot happen until the button down process is released.
I’m researching if there is a ability to have multiple lines in button text since some button description text gets a little long at times for a single line. I have tried a few carriage return linefeed command symbols in the text but that has not worked. So likely that is not the correct method or I'm doing it wrong.
I have come to realize now that for some buttons for which there is no stock pre-set action that I need to change those to hal push buttons instead of the hal action buttons in my gui. At least I think that is correct and as a sample I have included some info below.
The gui that I'm building for my mill has a fourth axis rotary, which can be configured as a indexer or used as a rotary rpm adjustable spindle. So I will be using the spindle hal action buttons for most of the buttons and give the objectnames, like "abtn_axis4_forward" or "abtn_axis4_stop".
For any hal push buttons used that have no predefined actions the objectnames for those buttons will have prefix "btn" instead of "abtn" like: "btn_axis4_spin_mode_enable" to change from indexer to spin mode on the 4th axis rotary.
I'm thinking about what it will take to display x number of mdi history commands and be able to click on those past issued commands so the clicked on one can be pasted into the mdi txt command line like gmocappy allows. This saves a lot of typing at times.
Getting close to needing to work on linking the gui into linuxcnc to update my hal file and make changes to the gui as needed. I will review your documentation on what needs to be done to get the pins to show up in linuxcnc.