You could rewrite the gizmo as a grizmo that reloads its internals based
on a path stored on the root node (if present).
c
On 08/25/2016 09:25 AM, Hugo Léveillé wrote:
You could always add a knob to the root and paste to path of you gizmo
location and add a onscriptload callback that looks for paths that
might have been added there and append them. That would be saved in
the script
But I am just throwing untested ideas there... Might encounter other
problem with this approach. But That's something worth testing
--
Hugo Léveillé
Head of 2D, MELS
hu...@fastmail.net
On Thu, Aug 25, 2016, at 09:20, Fredrik Averpil wrote:
@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
<mailto: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
--
SPINVFX
CHARLES TAYLOR / COMPOSITING SUPERVISOR
STUDIO/ 416-504-8333 <tel:4165048333>
SPINVFX.COM <http://www.spinvfx.com/>
CONFIDENTIALITY NOTICE: This e-mail message, including any attachments,
is for the sole use of the intended recipient's and may contain
confidential or proprietary information. Any unauthorized review, use,
disclosure or distribution is prohibited. If you are not the intended
recipient, immediately contact the sender by reply e-mail and destroy
all copies of the original message.
_______________________________________________
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
