The part you're missing is that variables in TCL are prefixed with $, so
Nuke thinks you're trying to reference one of those. Intelligent/automatic
environment variable expansion isn't really something you should ever expect
a program to do unless it's named *sh.
When you call [getenv $ENV_VAR], you're still invoking the TCL parser, but
you're calling an actual TCL function (getenv).
Hope this makes sense.
-Nathan
-----Original Message-----
From: [email protected]
Sent: Thursday, November 17, 2011 1:35 AM
To: [email protected]
Subject: [Nuke-users] Nuke variable question
We enforce cross-platform compatibility using environment variables
($ENV_VAR/path) in our file dependencies. It seems like Nuke (which
we're just starting to use on our farm), doesn't expand variables by
default - only when set as:
[getenv ENV_VAR]/path
I'm aware that there are other ways to resolve filepaths in Nuke, but
I'm curious why "$ENV_VAR" isn't supported - apparently Nuke
recognizes that "$" designates a variable. If you use:
$ENV_VAR/path
in a file knob in Nuke, the error comes up as "can't read ENV_VAR: no
such variable".
Am I missing something basic here? Our compositing pipeline was
previously based around Shake, which had no problems expanding
variables in filepaths...
Cheers,
Daniel
_______________________________________________
Nuke-users mailing list
[email protected], http://forums.thefoundry.co.uk/
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
_______________________________________________
Nuke-users mailing list
[email protected], http://forums.thefoundry.co.uk/
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
