What I like doing is replacing all my gizmos with groups when I'm finished with a script. For archiving purposes. Exactly for that reason. There's a script on Nukepedia that does that called bakeGizmos.
Ron Ganbar email: [email protected] tel: +44 (0)7968 007 309 [UK] +972 (0)54 255 9765 [Israel] url: http://ronganbar.wordpress.com/ On 4 September 2012 10:48, sh4dow <[email protected]>wrote: > ** > *Diogo Girondi wrote:* Managing revisions and versions of grizmos in > scripts that are being versioned themselves can quickly become a real > nightmare. > > > Well but what about opening an old comp that uses a gizmo that has been > changed? An artist should always be able to rely on the fact that whatever > he used in the comp still works as it did back when he first created it. > > And of course not every little gizmo people create may make it to a > company's repository right away, in which case grizmos help should it be > necessary for a different artist to edit a comp. > > @ NathanR: > > So what function can be used to change class names? > > _______________________________________________ > Nuke-python mailing list > [email protected], http://forums.thefoundry.co.uk/ > http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python > >
_______________________________________________ Nuke-python mailing list [email protected], http://forums.thefoundry.co.uk/ http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python
