I’m not convinced this is a bug so much as everything seems to be working correctly.
If props.x is None (or doesn’t exist), and props.y is bound to props.x and then props.z uses props.y and runs the value of props.y through a script, then when that evaluation is run you are attempting to iterate over a NoneType Object.
If you’re setting a property to a non-changing value in a script, then it sounds like that property should just already have that value - instead of setting it at runtime.
In an attempt to see if everything was indeed working as intended, I set up a View the following way:
I placed a Button.
New Custom property Button.custom.x, with value = “null” (None).
New Custom property Button.custom.categoryValues, which is bound to Button.custom.x
New Custom property Button.custom.z, which is bound to Button.meta.name and includes a Script Transform:
xAxisValues = self.custom.categoryValues
logger = system.util.getLogger('REPLICATION')
for idx, xval in enumerate(xAxisValues):
logger.info(idx + xval)
return value
I actually get the same NoneType warning in the Designer, so everything seems to be working.
