What if
1. When you create the node you actually copy a gizmo script to a location with
a unique name. If it needs to work across all scripts rather than in the one
script then I guess skip the unique name
2. Have an update button in the node which effectively rewrites that gizmo with
all the changes and
3. replaces all nodes referencing that gizmo with the new one.
It would require stopping the user from making new uniquely named nodes, or a
function that would (like force clone) set all similar nodes to only one
version (and remove/archive the others?) of the external gizmo.
And it could check the script for the node and alert the user to whether or not
they wanted to start a new version or use a copy(clone) of the already created
version
Not as immediate but has the slight advantage that if you screw it up you could
always go back to another version in the script until you update.
Would that work?
Howard
>________________________________
> From: Thorsten Kaufmann <thorsten.kaufm...@mackevision.de>
>To: Nuke user discussion <nuke-users@support.thefoundry.co.uk>
>Sent: Monday, 29 April 2013, 16:44
>Subject: AW: [Nuke-users] "Referencing" or "Instancing" groups of nodes
>
>
>
>Thanks everyone,
>
>i am aware of node-by-node workarounds. This is not what I need though.
>Compers might add arbitrary nodes at any point or time, and
>preventing them from manually having to clone nodes around is the whole idea.
>So adding and removing nodes must happen automatically
>too.
>
>Von:nuke-users-boun...@support.thefoundry.co.uk
>[mailto:nuke-users-boun...@support.thefoundry.co.uk] Im Auftrag von Elias
>Ericsson Rydberg
>Gesendet: Montag, 29. April 2013 17:27
>An: Nuke user discussion
>Betreff: Re: [Nuke-users] "Referencing" or "Instancing" groups of nodes
>
>Hey,
>
>I have never had any issues with cloning nodes corrupting scripts, but if you
>have it makes sense you avoid it. The other approach would be to copy the
>network, link all knobs to the "master" network and use python callbacks to
>have all other copied networks inherit the change.
>
>I'm not sure it would work, but maybe give it a try?
>http://www.youtube.com/watch?v=az6A1BCDXzY
>
>Cheers,
>Elias
>
>2013/4/29 Thorsten Kaufmann <thorsten.kaufm...@mackevision.de>
>Hi there,
>
>i am aware of cloning, but you cannot clone groups. Also cloning has been an
>infinite source of agony here. Has this changed for 7? (Corrupt scripts
>that can only be “fixed” by removing clones via texteditor). In addition there
>are python tools to create a linked copy as opposed to a clone, but that
>also does not allow me to have a group of nodes being cloned. PreComp also
>won’t work because I need the ops to be in the script and editable
>live.
>
>Thanks and Regards,
>Thorsten
>
>Von:nuke-users-boun...@support.thefoundry.co.uk
>[mailto:nuke-users-boun...@support.thefoundry.co.uk] Im Auftrag von Elias
>Ericsson Rydberg
>Gesendet: Montag, 29. April 2013 16:22
>An: Nuke user discussion
>Betreff: Re: [Nuke-users] "Referencing" or "Instancing" groups of nodes
>
>I believe cloned nodes does just what you are after? If you change the value
>of a clone it will also affect the "parent". Simply select and Alt+K.
>
>I tried making a gizmo out a little network, but gizmos can't be cloned. At
>least not in 6.3.
>
>2013/4/29 Thorsten Kaufmann <thorsten.kaufm...@mackevision.de>
>Hey there,
>
>i am trying to find the best way to “instance” (clone?) a set of nodes.
>Basically I want to have a bunch
>of nodes that are then used at many different places within the script. When
>nodes are added/changed
>it needs to be updated everywhere. In an ideal world it would work somewhat
>like a group that can be
>cloned and expanded right within the script.
>
>Any pointers or ideas? Please note I am also open to NDK solutions if anybody
>has done anything
>Similar (e.g. would it be a feasible way to have a node that internally
>recreates a nodetree of
>A specified group and acts like a clone?).
>
>Kind regards,
>Thorsten
>Thorsten Kaufmann
>Head of Production
>
>________________________________
>
>Mackevision Medien Design GmbH
>Forststraße 7
>D-70174 Stuttgart
>T +49 711 93 30 48 59
>F +49 711 93 30 48 90
>M +49 151 19 55 55 02
>thorsten.kaufm...@mackevision.de
>http://www.mackevision.de
>Geschäftsführer: Armin Pohl, Joachim Lincke, Karin Suttheimer
>HRB 243735 Amtsgericht Stuttgart
>
>
>_______________________________________________
>Nuke-users mailing list
>Nuke-users@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/
>http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
>
>
>_______________________________________________
>Nuke-users mailing list
>Nuke-users@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/
>http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
>
>_______________________________________________
>Nuke-users mailing list
>Nuke-users@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/
>http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
>
>
_______________________________________________
Nuke-users mailing list
Nuke-users@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
