Yup. To clarify, I know that the function called a script. The question is: soes anyone know what the function actually is?
As I understand it, a plug-in stores (or can store) one or many custom functions for use in calculations.
Unfortunately, I don't code C++, and can't get into it.
Do you need to know how it did what it did if you know what it did? (I also don't want to read C++ code, which is one of the joys of built-in script triggers.)
A script trigger set to run when exiting the field should be able to replicate the functionality of the plugin since the scripts being triggered are already part of the file system, so you can see what they would do.
Or am I missing something?
Yes. To know "how it did" what it did.
There are an awful lot of fields that are validated through the returned vale of calculations using XMpl_StartScript.
Using script triggers hasn't (yet) replicated the plugin's behavior.
Thanks for responding.