Hi John,
IMO, this is yet another case that reveals the need to have a
<knob>.changed() method to force-trigger callbacks associated with changing
a knob.
In this case, though, you can force the required changes by setting and
unsetting the KNOB_CHANGED_RECURSIVE flag.
k = <your_knob_object>
k.setFlag(nuke.KNOB_CHANGED_RECURSIVE)
k.setLabel('newLabel')
k.clearFlag(nuke.KNOB_CHANGED_RECURSIVE)
On Thu, Jan 19, 2012 at 11:52 AM, John Vanderbeck <
[email protected]> wrote:
> **
>
> I just wanted to check if anyone else is seeing this behavior, and
> possibly is aware of a workaround?
>
> If I call setLabel() on a knob, in my case specifically a series of
> Boolean_Knobs, the actual label does not change until the user closes the
> properties panel for that node, and reopens it. Once reopened, the correct
> labels are shown.
>
> I thought I might work around it by scripting the panel to close then open
> using node.hidecontrolPanel() and node.showControlPanel(), but then I ran
> into another issue where the back to back calls don’t work. The panel
> will close, but not open when the function is called.
>
> John Vanderbeck
>
> Technical Artist
>
> Digital Domain Media Group
>
> NOTICE: This communication may contain privileged or other confidential
> information. If you have received it in error, please advise the sender by
> reply email and immediately delete the message and any attachments without
> copying or disclosing the contents. Thank you.
>
>
> _______________________________________________
> Nuke-python mailing list
> [email protected], http://forums.thefoundry.co.uk/
> http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python
>
>
_______________________________________________
Nuke-python mailing list
[email protected], http://forums.thefoundry.co.uk/
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python
