@Charles: Yes, we actually convert most of our gizmos to groups for this exact reason. This time, however, we're looking to keep the "reference" to the gizmo on disk, so that in case we change the gizmo these changes are propagated onto all Nuke scripts that are using it.
@Hugo: About the Grizmo approach, I don't want the gizmo to be killed into a group. I want the connection back to the external file that is the gizmo. So, I'm trying to figure out a way to make the Nuke script itself be aware of a gizmos location. So that when opening the script, it will also recognize any gizmos. A great solution would be if any gizmo residing in the same directory as the script itself would automatically be loaded. This however does not work. I guess it's "feature request time"!
_______________________________________________ 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
