bhavesh pandey

auto file = static_cast<const char *>(argv); // Filename or Op path
GU_SopQuery qsop;
auto handle = qsop.getDetail(file, -1);
auto gdp = handle.readLock();


I also came across GU_VexGeoInputs in the GU_SopResolver header..however, I could not get that to work.

If anyone knows of a better way I would be very happy

The following line will add points or prims to a group named after the “@group_”

@group_NAME_OF_GROUP = 1;

Alternatively, use:
setpointgroup / setprimgroup etc functions.

for setting Attribs:
i@foo = value;

where (from left to right):
1: i = attrib Type (in this case an int)
2: @ is used for binding the Attribute to the name fooo
3: foo name of attr
4: value = attr value = Attrib type.

I find these more convenient than using VOPs.
All this is already documented the Help Docs.

As far as Attrib Vops are concerned, setattribute wont work because
it expects the attribute to already exist on Geo.
I would rather use Bind vop to write out attributes, its less hassle.

ArrayType returning functions are allowed and do work, just not in the Wrangle SOPs (ie. when defined inside the Wrangle SOPs).

But they do work if you define these in an external source file which is then included into your Wrangle SOP using the include directives.

The same goes for structs (custom data structures with member functions are supported) and I really like somethings about this. However the one thing I feel missing is Data persistence with Structs (ie. we cant read the data from another Wrangle node or store these on points as attributes). I have however found some workarounds to those.

Congratulations to the team at SESI! This release is really smashing!