I’d like to expose a sort of “status flag” from a plugin to the interface level using a Boolean_knob, so it can be expression-linked, etc. but not edited. My plugin currently has a member bool that is set in _validate() and used to make decisions in request() and engine(); picture a Switch node where the switching decision is made automatically, but you still want to expose some kind of a knob indicating which one is actually being used.
The obvious choice seems to be to just piggy-back a new Boolean_knob on that existing bool, but when I do this, the knob doesn’t update when the bool changes (presumably because it doesn’t know it needs to). Is this a “safe” way to do things? If so, what’s the most efficient way to force my knob to update from its “storage variable?” Or should I just add another variable to store the knob’s state and call set_value on the knob directly when it needs to change? Thanks, -Nathan
_______________________________________________ Nuke-dev mailing list [email protected], http://forums.thefoundry.co.uk/ http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-dev
