If you there isn't anything on the current session that worths saving you could do:
nuke.Root().setModified( False ) nuke.scriptOpen( filepath ) It should save you blink and open the file on the current session :) Cheers, Diogo On Mon, Sep 8, 2014 at 3:24 AM, Fredrik Averpil <fredrik.aver...@gmail.com> wrote: > Thanks for explaining that Diogo. I managed to do what I needed to do with > > nuke.scriptClear() > nuke.scriptOpen( filepath ) > > Regards, > Fredrik > > > > On Sun, Sep 7, 2014 at 10:07 PM, Diogo Girondi <diogogiro...@gmail.com> > wrote: > >> Depending on what you're doing you have to first set the Root modified >> state back to false by adding a "nuke.Root().setModified(False)" otherwise >> Nuke will understand that whatever it needs to do, must be done in a new >> session. >> >> If you need to check if a script is modified or not, use "nuke.Root(). >> modified()". >> >> >> Cheers, >> Diogo >> >> On Thu, Aug 21, 2014 at 11:44 AM, John Vanderbeck <jwvanderb...@gmail.com >> > wrote: >> >>> 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 >>> >>> >> >> _______________________________________________ >> 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
