Can you give an example of how to use nuke.DO_NOT_WRITE on a pulldown knob?
I have some python that reads our database for sequences and shots, then creates a gizmo and populates a cascading pulldown with those results. Those values are gone when you reload the script. So, I have a similar issue to this thread, but I cannot figure out how to assign the nuke.DO_NOT_WRITE to the specific knob. thx Dan On Thu, Oct 27, 2011 at 5:42 PM, Mark Boorer <markboo...@fuelvfx.com> wrote: > Thanks Nathan! > > That worked like a treat :) > > Cheers, > Mark > > > On 10/24/2011 12:51 PM, Nathan Rusch wrote: > > 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 > > -- > This message was scanned by Fuel's spambox and is believed to be clean. > Click here to report this message as spam. > > > _______________________________________________ > 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