QtPyVCP Widget Rules

Widget Rules is a powerful feature of QtPyVCP but can be a bit overwhelming at first so I expanded the QtPyVCP documents with a step by step explanation of widget rules.

www.qtpyvcp.com/widgets/rules.html

If you see anything missing or wrong let me know. I just want users to be able to use the power of Widget Rules.

JT

Awesome work. Thanks.

In the status:gxxoffset channel tuple the R value is not available. Currently only 9(0- values are there. XYZABCUVW.

How hard is it to add the R value? It makes displaying the R value of the current WO index hard to display outside the table.

Thanks. Don

That is not provided by LinuxCNC on that status item. I have no clue where the python module is in LinuxCNC

linuxcnc.org/docs/2.8/html/config/python...xcnc_stat_attributes

JT

Understood. Most likely in the linuxcnc binary files. That said, it would be nearly impossible to change without the source.

LinuxCNC is open source
github.com/linuxcnc

JT

Hello. When adding spindle speed with the slider, the speed in hal show changes, but not in the indicator. Can this be fixed with Widget Rules?

Don, I thing the data you are looking for is available from the `status:rotation_xy` data channel.

hottabich, yes, you can do almost anything with rules!

The `status:spindle.0.speed` value is the programmed spindle speed (always matches the value of the last S word in gcode). So to get the actual commanded spindle speed you need to multiply by the spindle override, which is available as `status:spindle.0.override`.

KCJ wrote: hottabich, yes, you can do almost anything with rules!

The `status:spindle.0.speed` value is the programmed spindle speed (always matches the value of the last S word in gcode). So to get the actual commanded spindle speed you need to multiply by the spindle override, which is available as `status:spindle.0.override`.

Thanks, it works!