FYI what is happening here is that Nuke decides whether or not to open a new instance based on whether or not the current script has changes in it. So by making Nuke a fresh slate first, it then will load the script into the existing instance.
- John Vanderbeck - http://www.johnvanderbeck.com On Thu, Aug 21, 2014 at 6:37 AM, Fredrik Averpil <fredrik.aver...@gmail.com> wrote: > Thanks, that worked! > > Regards, > Fredrik > > > On Wed, Aug 20, 2014 at 6:15 PM, Erwan Leroy <er...@erwanleroy.com> wrote: > >> Try clearing the script then opening maybe? >> On 20 Aug 2014 16:57, "Fredrik Averpil" <fredrik.aver...@gmail.com> >> wrote: >> >> Hi, >> >> The command nuke.scriptOpen() opens up the script in a new Nuke window. >> Is there any way to open up the nuke script in the currently active window, >> where nuke.scriptOpen() is being executed? >> >> Regards, >> Fredrik >> >> >> _______________________________________________ >> 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 >> >> >> _______________________________________________ >> 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 >> >> > > _______________________________________________ > 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 > >
_______________________________________________ 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
