In a file with multiple configurations, I am using an IGNM operand to ignore a range of surfaces. I find that if I edit the range of surfaces in the operand properties, the boolean values (0/1) that I have defined for all configurations change in unpredictable ways. Sometimes they seem to reset to 0, sometimes to 1. I find it very inconvenient that I have to re-evaluate/re-assign boolean values to all configurations after editing the line item- it would be preferable if all assigned values remained the same after the change takes effect.
I wonder if there are other operands that change value assignments in unexpected ways when the operand properties are modified?
Best answer by Allie
View original