Are you using nuke.pluginAddPath or nuke.pluginAppendPath in your init.py? If
you’re using the latter, init.py and menu.py scripts in your added location
won’t be executed, because the plugin paths are traversed in reverse order.
If you’re not setting NUKE_PATH before launching Nuke at all, the setup is as
simple as this:
1) In ~/.nuke/init.py, call `nuke.pluginAddPath('/path/to/custom/directory')`
2) Place your central init.py and menu.py files in '/path/to/custom/directory'.
-Nathan
From: mailto:nuke-python-re...@thefoundry.co.uk
Sent: Wednesday, May 08, 2013 4:46 AM
To: nuke-python@support.thefoundry.co.uk
Subject: [Nuke-python] Re: menu.py not running automatically?
Hi Nathan
Thank you very much for your reply
I am very much in the experimentation al phase with Python atm. I have got
everything to work whilst the gizmos are inside my .nuke directory which is
fine.
I have not set the NUKE_PATH via terminal, what I have done is added the new
plugin path inside both my menu and init.py.
Nuke obviously knows where this is as all works well when I run the menu.py
script manually.
What I am guess I could do with knowing is why nuke is not executing the script
when it opens? Or am I running down the wrong avenue?
Thanks again
Simon
--------------------------------------------------------------------------------
_______________________________________________
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
