I'm not sure if you are on the right track (or indeed if you are using Gmocappy. I've circled the min value I was referring to in your earlier screen dump
Attachment not found
Having a value of 0 here limits the range to a positive value
But the Gmocappy python screen handler overwrites these values as this small snippet shows:
Code:
class PlasmaClass:
def __init__(self, halcomp, builder, useropts):
self.builder = builder
self.halcomp = halcomp
self.defaults = { IniFile.vars : { "thcspeedval" : 100 ,
"thcspeedmax" : 150 ,
"thcspeedmin" : 50 ,
"thcspeedincr" : 5 ,
and if you look at the Gmocappy plasma sim which I am more familiar with, you will see that these values are also stored in a .var file (plasma.var)
Code:
# generated by gladevcp.persistence.create_default_ini() on Sun Jul 30 15:06:09 2017
[ini]
version = 1
signature = 41e519529d06885683da34f0f6da60585d0d3676
[vars]
cutgapval = 1.5
thcdelaymax = 20.9
thcspeedincr = 5
chlthresholdmax = 100.0
thcspeedmin = 50
g0gapincr = 0.5
thcspeedmax = 150
piercegapmin = 2.0
enableheightlock = True
g0gapmin = 0.5
thctargetvoltval = 100.0
thctargetvoltmax = 255.0
thctargetvoltincr = 5.0
piercegapval = 5.0
g0gapmax = 55.0
piercedelaymax = 10.0
piercedelayval = 0.5
thctargetvoltmin = 5.0
thcspeedval = 100
cutgapmin = 0.5
enablekerfcross = True
piercedelayincr = 0.01
thcdelayincr = 0.1
chlthresholdmin = 10.0
piercedelaymin = 0.01
thcdelayval = 0.5
thcdelaymin = 0.1
cutgapincr = 0.01
chlthresholdincr = 10.0
piercegapmax = 12.0
g0gapval = 45.0
piercegapincr = 0.5
pierceutostart = True
chlthresholdval = 80.0
cutgapmax = 5.0
[widgets]
hal-btn-THC = False
# last update by gladevcp.persistence.save_state() on Sun Nov 12 07:13:20 2017
So for this screen, there is plasma.glade, plasma.py and plasma.var to take into account. In this case, I found you needed to change the plasma.py defaults and delete the plasma.var file before changes in glade actually stuck. I can't see why negative values are not allowed.
