andras liptak

Many thanks for the quick answer! I see now.

One more little thing: if the context is not specified explicitly in the doc does it mean the function is available in all context?
Like this:
http://www.sidefx.com/docs/houdini15.0/vex/functions/intersect [sidefx.com]

Hi All,
Am I totally missing some point here?

Isconnected should work… at least the docs says:
http://www.sidefx.com/docs/houdini15.0/vex/functions/isconnected [sidefx.com]

pusat

jlait
That parameter is there for future compatibility. If we didn't have it, we'd have painted ourself in a corner in the glorious future when you'll be able to edit other geomety's than your own.

Unfortunately, we do not yet live in that glorious future.

(My dream is to allow the Attrib VOP to have multiple outputs which you target with 0/1/2/3/4… But it is but a dream…)

Will this feature be used a lot? I can't think of many scenarios where you need to modify multiple inputs at once. I am probably not seeing the big picture but can you please give some practical examples?

From my part it was more of a conceptual / degree of freedom type of question. And also didn't want to miss an interesting feature or assume something irrational.

Example:
Imagine a buffer geometry where you can write / store diagnostics or other common data from different networks. In this case it would act like common storage / memory for all participating networks.
Sure, this can be solved in many other different ways, but that particular geohandle parameter was standing out unexplained.