A sidecar file is definitely another option, though you do still run the risk of things falling out of sync. If you are going to use one, though, I would recommend using something like ConfigParser/iniparse as the interface, as opposed to rolling your own input/output and formatting handlers.
Alternatively, you could just store your render options as a serialized dict (via pickle, JSON, etc.) on the root node in the script itself. -Nathan From: Marc Gutowski Sent: Tuesday, October 23, 2012 12:57 AM To: nuke-python@support.thefoundry.co.uk Subject: [Nuke-python] Re: Problem Calling Python script inside of .nk-File/ TCL hey, i would code Nathans way too. a further possibility to go with some advanced custom prefs for specific scene files would be a "txt" file, named exactly as the nk.scene file (actualizing with every saving, or deleting) containing custom function prefs, hooked up by your routine. this helps you, to don't memorize all function parameters, maybe in a nice input mask in the text file, e.g. path="" subfolder="" writenodes="" as nathan said, use the callbacks, e.g. OnSceneLoad -------------------------------------------------------------------------------- _______________________________________________ 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
