Hmm and have the script nab the various values from the array? Maybe I'm not looking at that right or even how it applies here so could you elaborate?

I was thinking, since I have a checkBox connected to say MR's fg attr, I would create a global var for the layout containing other ui elements that are fg related and create a scriptJob that's based on a change in the fg attr and enables/disables the layout and thus all its child controls. The custom condition would have allowed me to do that without having to define a global var but that's a no go. In this case I guess the global vars shouldn't be too much because there are really only so many Mr features, GI, FG, Caustics, AO and last but not least Raytrace which will have final say on whether all their controls will be enabled or not. Argh I'm babbling on.