ScriptDAT needs to notice a new custom parameter

TD 2018.23120 Windows 10

I have a question about the cook dependency of a script DAT that
counts the number of custom parameters of an OP.
It looks like adding a custom parameter doesn’t cook the script DAT, so
the count becomes inaccurate. I want it to be accurate, but on the
other hand, I don’t want the script DAT to cook for EVERY cook of the
target operator.

Instructions:

While inside /project1 but not inside base1,
use “Customize Components” to add a new Float parameter to base1.

Note that NumCustomParameters is still 1.0

Now go inside base1 and force cook ‘build_pars_script’.
NumCustomParameters should go up to 2.0

Is there an efficient way to keep NumCustomParameters accurate?
script_dat_cooking.1.toe (4.51 KB)

The Script DAT (or any expressions) should have re-cooked when the source operator was customized.

This is now fixed in 2018.23400.

A future version of the software will have a Parameters DAT though, which will make this even simpler.

Cheers,
Rob