by Achim » Wed Nov 28, 2007 2:45 pm
used it to supply basic viewport handles for my components UIs.
For parameters where I'd like to have a viewport handle, I create an extra null component. When the null is selected in the viewport, the geo select script enabled the "change" mode for a DAT inside the null. This DAT is monitoring a CHOP with the fetched channels from the null. Then any viewport interaction of the null cause the DAT to execute and it writes the values to a master table DAT (storing all UI parameters current values).
In return, when the values are changed via the UI (sliders), they are put into the master table DAT and opparmed to the null component. Also the "change" toggle in the null is turned off again to avoid recursion.