Set the flag nuke.DO_NOT_WRITE on your pulldown knob.
-Nathan
From: Mark Boorer
Sent: Sunday, October 23, 2011 5:52 PM
To: nuke-python@support.thefoundry.co.uk
Subject: [Nuke-python] Error on load of gizmo pulldown menu populated
viaonCreate
Hi folks,
My problem is that I have a gizmo containing a pulldown menu. The available
selection choices are empty by default, and populated via python when the node
is created, The user makes a selection, saves the script, and exits.
When the script is re-loaded, there are no available selection choices yet, but
nuke tries to set the selection to what was saved, bringing up the error
"Nothing is named".
I've seen examples where nodes are generated in python, but I'm not sure if
those translate to when the node is stored via a gizmo.
In the gizmo:
addUserKnob {4 tag l group M {""} }
Python:
n['tag'].setValues( ['item1','item2','item3'] )
I can't store all the selections in the gizmo, because they may be different
every time nuke is launched, not to mention that the gizmo is read only. Anyone
got any advice?
Thanks,
Mark
--------------------------------------------------------------------------------
_______________________________________________
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
