Python scripting of the parm template is very spotty. dialog script is the one true language for parameters, and many aspects are not implemented yet in the houdini python module. It might not be possible to change what you are looking for with python.
all node interfaces are internally stored as ‘dialog script’ a sort of json-esque language. if you unpack an otl, you will find dialog script inside that contains the names of all the parms, as well as the properties of each.
jsmack all node interfaces are internally stored as ‘dialog script’ a sort of json-esque language. if you unpack an otl, you will find dialog script inside that contains the names of all the parms, as well as the properties of each.
Thanks a lot! In fact, I thing there is a bug (or it is the normal behavior) but the enable flag for Range is always set back to Enable.
jsmack all node interfaces are internally stored as ‘dialog script’ a sort of json-esque language. if you unpack an otl, you will find dialog script inside that contains the names of all the parms, as well as the properties of each.
Thanks a lot! In fact, I thing there is a bug (or it is the normal behavior) but the enable flag for Range is always set back to Enable.
I will log a bug!
Did you ever find a fix for this? I'm noticing this as well on an HDA I'm working on where the Range is always defaulted to ‘on’. It's causing issues when I'm trying to destroy and create a new slider and automatically set the max range to the len(number of files). The PythonModule is printing the correct value but defining the max value for hou.IntParmTemplate() doesn't work, it's locked because the range slider is defaulting ‘on’ no matter what in the parameter settings.
jsmack all node interfaces are internally stored as ‘dialog script’ a sort of json-esque language. if you unpack an otl, you will find dialog script inside that contains the names of all the parms, as well as the properties of each.
Thanks a lot! In fact, I thing there is a bug (or it is the normal behavior) but the enable flag for Range is always set back to Enable.
I will log a bug!
Did you ever find a fix for this? I'm noticing this as well on an HDA I'm working on where the Range is always defaulted to ‘on’. It's causing issues when I'm trying to destroy and create a new slider and automatically set the max range to the len(number of files).
jsmack all node interfaces are internally stored as ‘dialog script’ a sort of json-esque language. if you unpack an otl, you will find dialog script inside that contains the names of all the parms, as well as the properties of each.
Thanks a lot! In fact, I thing there is a bug (or it is the normal behavior) but the enable flag for Range is always set back to Enable.
I will log a bug!
Did you ever find a fix for this? I'm noticing this as well on an HDA I'm working on where the Range is always defaulted to ‘on’. It's causing issues when I'm trying to destroy and create a new slider and automatically set the max range to the len(number of files).
jsmack all node interfaces are internally stored as ‘dialog script’ a sort of json-esque language. if you unpack an otl, you will find dialog script inside that contains the names of all the parms, as well as the properties of each.
Thanks a lot! In fact, I thing there is a bug (or it is the normal behavior) but the enable flag for Range is always set back to Enable.
I will log a bug!
Did you ever find a fix for this? I'm noticing this as well on an HDA I'm working on where the Range is always defaulted to ‘on’. It's causing issues when I'm trying to destroy and create a new slider and automatically set the max range to the len(number of files).
We just lived this that I think
I bug was entered in the bug report at SideFX
Yea I submitted a bug as well.
Could you give your bug number to “link” them together