(Solved) Probe Basic - HAL pins not being created

for reference here are the already linuxcnc exposed status items:

linuxcnc.org/docs/html/config/python-interface.html

As I said earlier, the LED was just a first attempt.  When that didn't work out, I realized a label that acted like an LED could do double-duty and save screen space.

Just so we're on the same page, here are two screenshots of what I've got after Claude created new .py and .qss files



The red one is actually blinking, but you get the idea.

I'm not completely sure about the architecture, but it looks like that python file creates two hal pins per Qlabel instance.  And links the label to a .qss setting via the standard Qt Qlabel's dynamic settings.  Screenshot of the dynamic properties:



The rest of the indicators follow the same process.  Two hal pins are created per label, I link one of the pins in post-gui, set the dynamic properties to a color, and they all work.

I've attached the files in case you're interested in what's backstage.  And I think the status_tab.py was also modified - and is what I'm not supposed to touch (auto-updated when probe_basic.ui is open).

The above is what I was trying to do with HalLabel widget rules, but couldn't.

Ok I see now, did you try just using a halbutton? If you just wanted color change I think that would work and be simple. Have to check, but I believe they are bidirectional.

Lcvette wrote:

Ok I see now, did you try just using a halbutton? If you just wanted color change I think that would work and be simple. Have to check, but I believe they are bidirectional.
 

No, it didn't occur to me to use a button as an indicator.  And I didn't want an on-screen button or control widget.

doesn't have to be, you can give it no focus, im tinklering with it now just about have it and it is pretty easy with no code changes and making more of them would be way faster and not require code changes for each instance

ok yeah this is what you want to do it is much cleaner with no code changes to hack it up, this is existing hal code and the button itself is none functional in the ui essentially becomes a label, you cannot click it or select it or do anything bu observe it physically.

you then just add your net in postgui.hal file and your off to the races!

here is the stylesheet used:

That's really slick!

Any thoughts on the three-state label I mentioned?

PAUSED state is blinking.

and i am adding a flashing property to button widgets because thats a good idea..

 

there is no 3 states only on off because you only have on and off hal output and this can only use a single hal reader

just an fyi why are you destroying the format and look of the ui.. your better than that!