Are you sure that ice has the ability to convert strings to references and not just the other way around, Matt?
On Mon, Feb 9, 2015 at 11:34 PM, Matt Lind <speye...@hotmail.com> wrote: > I cannot remember for sure, but I believe you cannot access the value of a > string parameter stored in a CustomParamSet from an expression because > expressions can only reference animatable parameters (eg; numbers, boolean, > vector, color, ...). Strings are not 'animatable' in Softimage. > > You can write a scripted operator, but the scripted operator will have the > same limitation as expressions with regards to strings, but can be worked > around if you embed a customparamset inside of another to give the scripted > operator backdoor access. > > However, I would steer you towards ICE as you should be able to recreate > any expression as an ICETree. ICE has the ability to work with strings and > convert them to references. You might have to jump through a couple of > hoops along the way, but the hoops can be compiled down into a compound and > reused to make life easier. Solve once, reuse many. > > > Matt > > > > > > > Date: Mon, 9 Feb 2015 16:07:29 +0000 > From: "Ponthieux, Joseph G. (LARC-E1A)[LITES]" <j.ponthi...@nasa.gov> > Subject: Custom Param Set > To: "softimage@listproc.autodesk.com" > <softimage@listproc.autodesk.com> > > > Hello, > > I have an expression. Part of that expression points to a camera. > > I'd like to have that reference point to a Custom Pset parameter where I > can provide the name of the Camera in the parameter. > > I tried this with the Camera name as Text, but it doesn't work. Apparently > it can't resolve the object name that way. > > There will be multiple expressions, each pointing to the same Camera, I > wanted to make this easy to edit the Camera name and have it propagate to > all the expressions. > > How would I do this? > > -- > Joey Ponthieux > LaRC Information Technology Enhanced Services (LITES) > MYMIC Technical Services > NASA Langley Research Center > __________________________________________________ > Opinions stated here-in are strictly those of the author and do not > represent the opinions of NASA or any other party. >
