I see. The company I'm working for at the moment has been using full paths
since they started. I did rebuild most of the scripts they had but I
haven't changed that.
It's easy enough to modify, but then we'll still have some issues with the
older scripts.
Thanks for the comment though, it seems I may have been looking at the
wrong problem.
I'll figure it out.
On Jan 5, 2015 3:04 PM, "Nathan Rusch" <[email protected]> wrote:
> The typical way in which gizmos are used is to add the directories
> containing the files to the Nuke plugin path and then just use
> `nuke.createNode` with the base name of the .gizmo file.
>
> So, for instance, if a gizmo file is named “MyCustomNode.gizmo”, you would
> create it using `nuke.createNode('MyCustomNode')`.
>
> -Nathan
>
>
> From: Erwan Leroy
> Sent: Sunday, January 04, 2015 10:42 PM
> To: Nuke Python discussion
> Subject: Re: [Nuke-python] platformPathRemaps
>
>
> Hi Nathan.
> At the moment when I load a script from, let's say, windows to linux, it
> comes up with an error.
> When double clicking the node, it comes up with a knob "command" that has
> as a value the path to that gizmo ("Z:/CORE/2D/NUKE/GIZMOS/xxxx.gizmo")
> As well as a second knob containing all the parameters for said gizmo.
> If I open the .nk in a text editor and search and replace Z:/ by my linux
> path, then it opens just fine.
>
> Could it be that my gizmo menu adds them the wrong way then?
> menu.addCommand(name, 'nuke.createNode("'+ path + '")', "")
> Where path is the full path to the gizmo, including the filename.
>
> _______________________________________________
> Nuke-python mailing list
> [email protected], http://forums.thefoundry.co.uk/
> http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python
>
_______________________________________________
Nuke-python mailing list
[email protected], http://forums.thefoundry.co.uk/
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python
