GladeVCP

To put what psha just said in different words:
PyVCP pins can only display or set the values of HAL pins. So, a PyVCP LED will light up if the value of the HAL pin that it is connected to in the HAL file is high.

Similarly, when you operate a PyVCP control, it changes the value of its corresponding output HAL pin.

GladeVCP can do this, just the same as PyVCP. However GladeVCP also supports Actions. An action would be something like calling an executable Python file, for example. So, you could have a GladeVCP button that runs a script file, but without having to set a HAL pin connected to an MDI_COMMAND pin which is in turn linked to a custom M-code which contains the file. The button can call the file _directly_.

piasdom wrote:

i know, that's what i thought. but from what i understand, they're saying
i can't link to action.

I think you are confusing "actions" with "pin values"

"Actions" are bits of code that get run when you operate a control. GladeVCP has that, PyVCP doesn't.

However, an LED is just an indicator, you can't interact with it with the mouse, so there is nothing to tell it to run an action script.

However,just like a PvVCP LED, a GladeVCP LED can be linked in HAL to a HAL pin, and it will change colour when the value of the HAL pin changes. (Which I am fairly sure is what you want)