Sorry, Steve, but I don't understand. Are you suggesting adding the open code into an __init__.py file to solve this? The only solution I've seen so far would be to add a callback that listens for "Root" node creation and run it then. I have yet to test if that would work in interactive mode.
Best, -tony On Mon, Mar 10, 2014 at 11:05 AM, Steve Booth <st...@boothsoft.com> wrote: > __INIT__? > > > > *From:* nuke-dev-boun...@support.thefoundry.co.uk [mailto: > nuke-dev-boun...@support.thefoundry.co.uk] *On Behalf Of *Tony Barbieri > *Sent:* Monday, March 10, 2014 7:58 AM > *To:* nuke-dev@support.thefoundry.co.uk > *Subject:* [Nuke-dev] Open file on startup > > > > Hello! > > > > I am trying to open a file on startup by using a custom open method > written in python. I am trying to run the open code either in an init.py > or menu.py that we use for our facility. Ideally this can happen in the > init.py. The code appears to be running correctly but it seems that the > file is zeroed out to a default scene due to it running "too early". > > > > Is it possible to open a file on Nuke launch without using the standard > command-line file flag but do it via python? > > > > Thanks! > > > > -- > -tony > > _______________________________________________ > Nuke-dev mailing list > Nuke-dev@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/ > http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-dev > > -- -tony
_______________________________________________ Nuke-dev mailing list Nuke-dev@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/ http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-dev
