Updating Old GladeVCP Files?

Thank you all. Now that the old vcp is working again, I can try making the modifications I need to do.

I'll post back with either the final results or additional frustrations when I can work on it again Monday.

When I tested the above code, it would change the text, but the color stayed black (no color changes)

It worked for me in the virtual sim environment, debian 12, glade 3.4 installed and axis.mm sim. It was embedded as sidepanel. And the screenshots made when set example pin true/false. 

Ok, I think I figured out why the label colors weren't changing. In Glade, I had a color defined in the label attributes. After I cleared that entry, then the color changing worked.

Now to work on my further modifications.

Here are my updated files that work (for now, until I change them again)

 

With further testing, I'm seeing one weird quirk that I can't quite figure out.

I would like the two sets of clamping radio buttons to also indicate the state of the clamps. Because the clamps can also be activated/deactivated by custom M-codes in g-code, or by set of physical buttons on a user panel on the other side of the machine, I added some hal pins in the call back file to set each radio button active. The real buttons and M-codes all work as expected as I want them to. But when I press the unclamp button in the GladeVCP the clamps, unclamp then reclamp, then unclamp again. (And I have not even connected or used any of the hal pins I've added yet.) The GladeVCP clamp buttons seem to be working correctly.

Any ideas?

So long ago to remember but if you want to use gcode and gui buttons to do the same thing, I seem to remember you need to manage it in the python screen handler. Sorry I no longer have an example.

I'm starting to get pissed off. This stupid Gladevcp just does not seem to want to cooperate. My two sets of radio buttons are just being stupid. There are 2 pairs with each button triggering a hal action MDI widget. Each of the Hal Action MDIs call either a small sub program or a custom M-code. A set for the left side and a right side and both are exhibiting the same behavior. I have the left unclamp radio button as the master in the left group. Pressing the left_clamp button works correctly and runs it's sub program activate the left side clamps in a sequence. I have the unclamp buttons call for a single custom M-code that releases all of the clamps at once. But when I press the unclamp button, it runs the clamp sequence, then unclamps. If I press the unclamp button(s) while the vcp screen already indicates that the radio button is in the unclamped state, then it behaves properly and only issues the unlcamp M-code.

My second problem, I also have a set of physical buttons on the other side of the machine that use Halui MDI commands to call the same sub programs and custom M-codes to clamp and unclamp. Those are working perfectly by themselves. I created some hal pins in the python call back that toggle each of the VCP radio buttons, so the screen can match and indicate the state of the clamps. If I disable eache the button's "Related Action" in glade, that all works perfectly. Pressing the clamp/unclamp buttons change the toggled buttons on the VCP like I'd like them to. But then the VCP buttons don't actually do anything. With the button's Related Actions turned on, it set up a loop, where when one of physical the buttons are pressed, the clamps start cycling on, off, on, off... continually. Well that's no good at all, but not surprising.

Any clues atll how to fix the first problem. So far everything I've tried either has no effect or stops the GladeVCP buttons from working.

I think I could work around the 2nd problem if I could fix the 1st one. I'd have the physical buttons simply trigger the glade buttons instead of calling the halui MDI commands. The other way would be to make the call back file change the active button on the VCP without activating the buttons action, but still let the button action work when pressed on the screen. But I don't know how to do that.

This may not help but this 2017 post shows how to update a gmoccappy screen handler from gcode which sounds like your problem 1
forum.linuxcnc.org/plasma-laser/32691-settings-from-g-code-file
Here different values are set using an analog input which is decoded and used to modify screen elements. eg 900 and 999 change screen settings.