Hi Peter,
I would think that if there was an existing sub-dir in the NUKE path then it
would be available to all users, but if the user had their own identically
named sub-dir then it would come up as [user] . Meaning that you would respect
the NUKE_PATH order of loading as to where was
hi guys,
that would certainly suite our workflow too. we are manually copying these to a
global location, but the way paul describes the idea seems pretty solid for the
way we would see it working too ...
ben
On 23/11/11 14:35, Paul Raeburn wrote:
Hi Peter,
I would think that if there was
Hi Paul,
Yes, currently all Toolsets get saved in the .nuke directory and must be
manually copied to a shared location if you'd like them to be made
available to ther users. I guess it would be possible to add a
preference for Toolset save location, but this could be have a potential
for
I started experimenting with a rewrite of the toolsets feature, which
added a share command.
You created toolsets in the normal way, and they were created in ~/.nuke/
Then there was a share button which had a mirror of the toolset list
(just like delete), which presented you with a list of
I'm trying to work out how to allow users to save toolsets for other people to
pick up. By default when you use the Create function, they get saved in your
~/.nuke/ToolSets directory. If you make a toolsets directory in the nukepath
elsewhere the menu items show up for everybody, which is
