Multi OPs custom par on COMPs produces path warning

Wishlist and RFEs
1

hi all,

i’m seeing a mismatch in behavior with multi-op inputs. if i type multiple ops (space-separated) into an op parameter on a COMP (e.g. a top parm, op parm, or comp parm), the parameter UI shows a warning like “unable to resolve path”. however, if i do the same thing on a glsl TOP’s “TOPs” parameter, there’s no warning, and hovering the mouse shows that each path resolves correctly.

is this expected? is there a way to make a custom op parameter on a COMP behave like the glsl TOP’s multi-op parm (i.e. resolve multiple ops without warnings)? should i be using a different parameter type or setting to indicate “multi-op”, or is the recommendation to use a string parm and parse it (e.g. with evalOPs) instead?

thanks for any pointers!

2

Hi @huitresix,

correct, we currently don’t have multi op custom parameters and no setting to make them behave like multi operator references.

the .evalOPs() does work on the op type custom parameters despite the warning flag and equally can be used on the string type parameter. There is no real recommendation on which of both to use with the op custom parameter having the benefit of the additional functionality when referencing only single operators.

We definitely have a ongoing RFE for this, we’ll add your note to it.

hope this helps
cheers
Markus

1 Like
3

Thanks again for your answer Marcus.