#hazzy Logs

Jul 28 2020

08:36 PM hands[m]: so for instance I have the section with the Estop and power button and codeblocks in a widget, how to I expose the hal labels for runtime out to the HAL as they aren't in the compiled [skin]_ui.py after a Qcompile
08:43 PM -!- #hazzy mode set to +o by ChanServ
08:55 PM hazzy-m: hands: does that composite widget have a py file?
08:57 PM Joco[m]: Also remember some of these react to the LinuxCNC state and doesn’t in themselves need to expose Hal pins.
08:58 PM Joco[m]: * Also remember some of these react to the LinuxCNC state and don’t in themselves need to expose Hal pins.
09:15 PM Not-c0dc: [02probe_basic] 07TurBoss commented on issue 03#18: Program and machine labels drawn twice - 13https://git.io/JJuub
09:15 PM Not-c0dc: [02probe_basic] 07TurBoss closed issue 03#18: Program and machine labels drawn twice - 13https://git.io/JJZIL
09:17 PM TurBoss: hands: maybe this https://www.qtpyvcp.com/hal.html
09:18 PM hazzy-m: hands: any HAL pins should still get exposed, just need to make sure they don't have duplicate names
09:19 PM hazzy-m: here is an example of the HAL pins generated by the composite DRO widget used in blue control
09:19 PM * hazzy-m sent a long message: < https://matrix.org/_matrix/media/r0/download/matrix.org/tdCXSntkCHxuirZjLIzRLlEp >
09:25 PM hazzy-m: and the relevant bit of code in the composite widget py file:
09:25 PM hazzy-m: https://github.com/KurtJacobson/blue-control/blob/master/blue_control/widgets/composite_dro/composite_dro.py#L48
09:29 PM hands[m]: I'll check out dro label and see if it shares..
09:29 PM hands[m]: as for that halcmd do I run that wile LinuxCNC is running so there is some context to the run
09:30 PM hazzy-m: yes, LCNC should be running, otherwise there won't be any hal pins to look at!
10:06 PM hands[m]: thanks! I'll give that a shot