Expanding Environment Variables?

[dee900]

Is there a single API call for expanding a file string containing $HIP, $F and similar variables into its fully-qualified path?

[edward]

Take a look at CH_Manager::expandString(). Something like this:

UT_String expanded;

OPgetDirector()->getChannelManager()->expandString("$F $HIP", expanded);

[Jason]

Hey Edward,

On this topic:

Do you know if there is a method in the HDK to evaluate parameters to a certain depth?

Why? Often we make HDAs with, say, a File SOP or a ROP which refer to/channel-reference parameters on exposed by the HDA - which'd often contain $F4's and such - and what happens is that we'd like to follow the channel reference but not expand the $F4 in the destination string.

i.e.,

ropnet1/mantra1/picture: `chs("../../mypicture")`

mypicture : "/mydir/myfile.$F4.pic"

Performing a chsraw returns the string "`chs("../../mypicture")`

..and performing a chs returns the string: "/mydir/myfile.0001.pic"

..when I really want: "/mydir/myfile.$F4.pic"

We have workaround for this; and it's not pretty; and it's specific to how were submit things to the farm at DD, etc. A pretty large percentage of FX-related OTL systems have this need and the trick for getting it to work is like sacred knowledge.

In actual practice it would be fantastic to have the capability to specify evaluation depth and evaluation "features".

chseval( parm, depth, feature )

.eg.: chseval("../../picture", 1, EVAL_NO_VARIABLES )

..would be nice

Right now I'd settle for the knowledge if the HDK can handle this currently; any idea?

[edward]

In OP_Parameters, there's followChannelReferencesOneStep(). However, it only works for "pure" channel references (like those created by auto-linking HDA parameters).

[Jason]

In OP_Parameters, there's followChannelReferencesOneStep(). However, it only works for "pure" channel references (like those created by auto-linking HDA parameters).

That might suffice for most applications, thanks Edward. I'd think this would be useful function to expose in Houdini 9 since we do do this quite often - as I'm sure other people do.

[sibarrick]

Personally i always split the path and the frame into two parameters on the rop - often more.

Like project path, shot path, camera path, filename, frame number.

The downside to that is you have to build the references inside the HDA yourself and string alll these things together, that plus there is no file picker for HDA's that only let you pick a folder and not an actual file.

So my rfe related to this topic would be to have a folder picker option for file paths.

[edward]

I don't know if you guys are directing this at me or not but if you have RFEs, you should email them into support.

[dee900]

OPgetDirector()->getChannelManager()->expandString("$F $HIP", expanded);

Thanks Edward - that does it.

A general Odforce question to Jason, is it possible to have email notification of responses on by default? I couldn't find this in the personal settings ...

[dee900]

A general Odforce question to Jason, is it possible to have email notification of responses on by default? I couldn't find this in the personal settings ...

Of course I found this immediately after posting. Apologies for the two needless notifications.