Nuke 6.3 introduced a regressive bug that prevents knobs from being removed and re-added to a node, and likely prevents what you’re trying to do as well (knob copying).
The bug is logged as #20359 if you want to give it a support bump. You should add your use-case as well, just to make sure the issue stems from the same regression. -Nathan From: Matthew Doll Sent: Wednesday, October 17, 2012 10:13 AM To: Nuke Python discussion Subject: [Nuke-python] Copy custom knobs from one node to another? Howdy folks, I've got some code that used to work flawlessly but in one of the more recent version of Nuke it stopped working... newCtrls.addKnob(oldCtrls[knobName]) used to function... The goal is that I'm trying to allow the user the option where to insert NEW custom knobs. So I loop through and get all the existing knobs, ask the user where they want to insert the new knob, create a new node, copy all knobs up until the insert point, create new knobs, then add all the remaining old knobs onto the new node, then delete the old node. This is the only method I know of to insert a knob onto an "existing" node. Anyone have better suggestion, or could you help me with this no longer functioning code? newCtrls.addKnob(oldCtrls[knobName]) now throws the error "knob already attached to node". I can't do a .fromScript() because I need to create the proper knob type first. Thanks, Matt -------------------------------------------------------------------------------- _______________________________________________ Nuke-python mailing list Nuke-python@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/ http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python
_______________________________________________ Nuke-python mailing list Nuke-python@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/ http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python
