This is something completely random for me under OSX. Sometimes it does the expected which is to close the current instance and start a new blank one and other times it simply quits Nuke and leaves you waiting for the new instance to start. Something that never happens.
Under Windows on the other hand this is pretty consistent and will always close the current script and then start blank new one. - diogo On Sun, Mar 6, 2011 at 8:33 AM, Ron Ganbar <[email protected]> wrote: > HI all, > just finalizing bits in the book (see other thread about Nuke > 101<http://www.amazon.com/Nuke-101-Professional-Compositing-Effects/dp/0321733479/ref=sr_1_1?ie=UTF8&qid=1298978135&sr=8-1> > ). > > Wee discussion between myself and my Tech Editor. For you guys that are > using Macs. If you have a script open in Nuke and you save or don't save, > but press Cmd-W what happens? > A) Nuke quits all together? > B) Nuke clears the DAG and you get a fresh copy of Nuke? > > Answers will be appreciated. > > Thanks, > Ron Ganbar > email: [email protected] > tel: +44 (0)7968 007 309 [UK] > +972 (0)54 255 9765 [Israel] > url: http://ronganbar.wordpress.com/ > > _______________________________________________ > Nuke-users mailing list > [email protected] > http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users > >
_______________________________________________ Nuke-users mailing list [email protected] http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
