Setting initval of a spinbox in hal
21 Apr 2013 23:20 #32966
by ArcEye
Replied by ArcEye on topic Setting initval of a spinbox in hal
Hi
Quick answer - No
The value is set at either 100 or <initval> in the .xml file if set.
By the time the pins are available, the panel has been created from the .xml file
Long answer - Anything is possible, if you want to do it.
Have a look at /usr/share/pyshared/pyvcp_widgets.py
The code for the spinbox widget starts at line 763
You could rewrite the widget so that it creates a param called initparam and updates when this changes.
And here it is working - ignore the other stuff, I just added it to a sim to test it
This is not polished, I am not a python programmer, but it works.
(you need to delete /usr/lib/python2.6/dist-packages/pyvcp_widgets.pyc and insert this code into pyvcp_widgets.py or it will run the old compiled code)
regards
Quick answer - No
The value is set at either 100 or <initval> in the .xml file if set.
By the time the pins are available, the panel has been created from the .xml file
Long answer - Anything is possible, if you want to do it.
Have a look at /usr/share/pyshared/pyvcp_widgets.py
The code for the spinbox widget starts at line 763
You could rewrite the widget so that it creates a param called initparam and updates when this changes.
class pyvcp_spinbox(Spinbox):
""" (control) controls a float, also shown as text
reacts to the mouse wheel
<spinbox>
[ <halpin>"my-spinbox"</halpin> ]
[ <min_>55</min_> ] sets the minimum value to 55
[ <max_>123</max_> ] sets the maximum value to 123
[ <initval>100</initval> ] sets intial value to 100 TJP 12 04 2007
</spinbox>
"""
# FIXME: scale resolution when shift/ctrl/alt is held down?
n=0
def __init__(self,master,pycomp,halpin=None, halparam=None,
min_=0,max_=100,initval=0,resolution=1,format="2.1f",**kw):
self.v = DoubleVar()
if 'increment' not in kw: kw['increment'] = resolution
if 'from' not in kw: kw['from'] = min_
if 'to' not in kw: kw['to'] = max_
if 'format' not in kw: kw['format'] = "%" + format
kw['command'] = self.command
Spinbox.__init__(self,master,textvariable=self.v,**kw)
if halpin == None:
halpin = "spinbox."+str(pyvcp_spinbox.n)
pyvcp_spinbox.n += 1
self.halpin=halpin
if halparam == None:
halparam = "spinbox.initparam"
self.halparam=halparam
if initval < min_:
self.value=min_
elif initval > max_:
self.value=max_
else:
self.value=initval
self.oldvalue=min_
self.init=self.value
self.oldinit=self.init
self.format = "%(b)"+format
self.max_=max_
self.min_=min_
self.resolution=resolution
self.v.set( str( self.format % {'b':self.value} ) )
pycomp.newpin(halpin, HAL_FLOAT, HAL_OUT)
pycomp.newpin(halparam, HAL_FLOAT, HAL_IN)
self.bind('<Button-4>',self.wheel_up)
self.bind('<Button-5>',self.wheel_down)
pycomp[self.halparam] = self.init
def command(self):
self.value = self.v.get()
def update(self,pycomp):
pycomp[self.halpin] = self.value
if self.value != self.oldvalue:
self.v.set( str( self.format % {'b':self.value} ) )
self.oldvalue=self.value
self.init = pycomp[self.halparam]
if self.init != self.oldinit:
self.v.set( str( self.format % {'b':self.init} ) )
self.oldinit=self.init
self.value=self.init
def wheel_up(self,event):
self.value += self.resolution
if self.value > self.max_:
self.value = self.max_
def wheel_down(self,event):
self.value -= self.resolution
if self.value < self.min_:
self.value = self.min_
# -------------------------------------------
And here it is working - ignore the other stuff, I just added it to a sim to test it
This is not polished, I am not a python programmer, but it works.
(you need to delete /usr/lib/python2.6/dist-packages/pyvcp_widgets.pyc and insert this code into pyvcp_widgets.py or it will run the old compiled code)
regards
Please Log in or Create an account to join the conversation.
22 Apr 2013 15:23 - 22 Apr 2013 15:28 #32980
by ArcEye
Replied by ArcEye on topic Setting initval of a spinbox in hal
Hi
Have amended the code slightly so that the initparams number the same as the spinboxes
If you name your spinboxes with a suffixed number starting at 0, as I did, it is easy to see which initparam matches which spinbox
The new code is
and 'proof of life'
Don't forget to delete all the .pyc files, replace the various .py files with symlinks to /usr/share/pyshared/pyvcp_widgets.py and then you won't get into difficulties with old code being used.
regards
Have amended the code slightly so that the initparams number the same as the spinboxes
If you name your spinboxes with a suffixed number starting at 0, as I did, it is easy to see which initparam matches which spinbox
The new code is
class pyvcp_spinbox(Spinbox):
""" (control) controls a float, also shown as text
reacts to the mouse wheel
<spinbox>
[ <halpin>"my-spinbox"</halpin> ]
[ <min_>55</min_> ] sets the minimum value to 55
[ <max_>123</max_> ] sets the maximum value to 123
[ <initval>100</initval> ] sets intial value to 100 TJP 12 04 2007
</spinbox>
"""
# FIXME: scale resolution when shift/ctrl/alt is held down?
n=0
def __init__(self,master,pycomp,halpin=None, halparam=None,
min_=0,max_=100,initval=0,resolution=1,format="2.1f",**kw):
self.v = DoubleVar()
if 'increment' not in kw: kw['increment'] = resolution
if 'from' not in kw: kw['from'] = min_
if 'to' not in kw: kw['to'] = max_
if 'format' not in kw: kw['format'] = "%" + format
kw['command'] = self.command
Spinbox.__init__(self,master,textvariable=self.v,**kw)
if halpin == None:
halpin = "spinbox."+str(pyvcp_spinbox.n)
self.halpin=halpin
if halparam == None:
halparam = "spinbox.initparam."+ str(pyvcp_spinbox.n)
self.halparam=halparam
pyvcp_spinbox.n += 1
if initval < min_:
self.value=min_
elif initval > max_:
self.value=max_
else:
self.value=initval
self.oldvalue=min_
self.init=self.value
self.oldinit=self.init
self.format = "%(b)"+format
self.max_=max_
self.min_=min_
self.resolution=resolution
self.v.set( str( self.format % {'b':self.value} ) )
pycomp.newpin(halpin, HAL_FLOAT, HAL_OUT)
pycomp.newpin(halparam, HAL_FLOAT, HAL_IN)
self.bind('<Button-4>',self.wheel_up)
self.bind('<Button-5>',self.wheel_down)
pycomp[self.halparam] = self.init
def command(self):
self.value = self.v.get()
def update(self,pycomp):
pycomp[self.halpin] = self.value
if self.value != self.oldvalue:
self.v.set( str( self.format % {'b':self.value} ) )
self.oldvalue=self.value
self.init = pycomp[self.halparam]
if self.init != self.oldinit:
self.v.set( str( self.format % {'b':self.init} ) )
self.oldinit=self.init
self.value=self.init
def wheel_up(self,event):
self.value += self.resolution
if self.value > self.max_:
self.value = self.max_
def wheel_down(self,event):
self.value -= self.resolution
if self.value < self.min_:
self.value = self.min_
# -------------------------------------------
and 'proof of life'
Don't forget to delete all the .pyc files, replace the various .py files with symlinks to /usr/share/pyshared/pyvcp_widgets.py and then you won't get into difficulties with old code being used.
regards
Please Log in or Create an account to join the conversation.
23 Apr 2013 18:21 - 23 Apr 2013 21:49 #33050
by ArcEye
Replied by ArcEye on topic Setting initval of a spinbox in hal
Hi
If you or anyone else wants to, this patch will change the spinbox, scale and dial widgets, so that there is a parameter pin which allows the initial setting through HAL.
EDIT: It is not just for initialisation, it can be used to change the value displayed and output directly.
The methodology and naming is the same as I did for the spinbox, if you number your widgets with a suffix starting at 0, they will match the relevant initparams.
I don't know how generally useful this is, so don't think I will bother submitting for inclusion in the release.
regards
(rename to params.patch)
If you or anyone else wants to, this patch will change the spinbox, scale and dial widgets, so that there is a parameter pin which allows the initial setting through HAL.
EDIT: It is not just for initialisation, it can be used to change the value displayed and output directly.
The methodology and naming is the same as I did for the spinbox, if you number your widgets with a suffix starting at 0, they will match the relevant initparams.
I don't know how generally useful this is, so don't think I will bother submitting for inclusion in the release.
regards
(rename to params.patch)
Please Log in or Create an account to join the conversation.
Time to create page: 0.140 seconds