Setting initval of a spinbox in hal

I think you have found the right one.
Just in case another one it is free for personal and non commercial use.

I love this forum , every day is a learning experience . :woohoo:
Thank you masters.


bigalex :blink:

I'm watching to see what you find...

Finally getting somewhere.

To debug a running pyvcp panel, you first need to start Axis in another screen to have a linuxcnc instance which the component can register with and create pins etc
You could probably do it through halrun, but this is easier.
(You must halt and re-start each session or you will get duplicate component errors trying to create another pyvcp component)

Then from a terminal run winpdb pyvcp ./nameofxml.xml

This will allow you to step through and create the panel whilst examining all the structures



What I had not appreciated was that the widgets used in pyvcp are not tkinter widgets but the extended tkinter bwidgets from jeplers bwidget.py

Knowing that I have now found out why the tkinter method Label.set("Text") did not work.

Now I have used the bwidget Label.config(..) method and eureka I can reset the label text at will :woohoo:

I will return to it tomorrow, but selection of per-defined text fields, such as "On" / "Off" is definitely achievable.
If I create a bit pin as a trigger for each field it should be possible to link those to the signal associated with a button say
and then the text would change dependent upon which button is active.

Need to give that side of it a bit more thought, rest my grey cells for now.

regards

A m a z i n g ! ! ! :woohoo:
If you can upgrade the usabilty of the pyVCP widgets a lot of people will deeply appreciate.
Thank you ArcEye.

bigalex :blink:

OK, think it is sorted.

I have written a new widget called pyvcp_multilabel
It can display up to 6 different legends in the label text field, each one has a triggering bit pin which can be linked to anything suitable
It will display the text associated with the last pin triggered, so if you want to display one and then another you will have to leave a pause between triggers

The .xml format is
The hal pins are created basename.widgetnumber.legendN
so in the above example the first pin would be
EDIT: pyvcp.multilabel.0.label0

Below is proof of concept screen print
EDIT: (the hal pins still have old experimental names, now set as per above to prevent huge unweildly pin names based on label text)




I have attached a zip of the new pyvcp_widgets.py to replace your old one with and a directory to be inserted into your /home/you/linuxcnc/configs directory,
which will run the example above and allow you to see how widget pins were linked etc.

In the absence of any major reported problems, once I have finished some other stuff I will add this to the patch submission

regards

EDIT:
Amended file to fix oversight which would have led to very long pin names

Hi ArcEye.
What to say ... thank you.
This feature is very nice and useful .
One question ... please do not blame me.
Are you using a "tuple" for the text list ?
To make this widget more flexible is it possible to have instead of boolean pins an integer (unsigned) pin
to define which text have to be displayed ?

bigalex :blink:

Are you using a "tuple" for the text list ?
To make this widget more flexible is it possible to have instead of boolean pins an integer (unsigned) pin
to define which text have to be displayed ?

The code is in the zip.

I have not used tuples, they just seem to be some sort of inflexible, bastardised string array.
Python lists are just string arrays too, you can index through them just as easily.

Far from making the widget more flexible, restricting the ability to trigger label text changes, to widgets or components that can emit the correct s32 or u32 value, would reduce its flexibility hugely.
Most state changes are signalled by a bit pin flag, the appropriate bit pin in the widget can just be linked to it in a hal file.

If you want to make changes for your own special purposes then feel free, that is what open source is about.

regards