Ok solution found. I just added the considered reference's primitive in the operator outputs port list (before the UserDataBlob which is a output also) and now the operator is automagicaly attached to the operator stack at right place, no more at the UserDataBlob property. Now I get the mesh coordinates at modeling level.
Rémi 2012/8/21 Rémi Arquier <[email protected]> > Hi list, > > I have a custom C++ operator attached to a UserDataBlob (Property of the > X3DObject) and I would need to get the geometry at Modeling stack level => > siConstructionModeModeling. The custom operator takes as input port a ref > of a primitive and ouput a UserDataBlob. > > I saw the method Primitive::GetGeometry(double inTime, siConstructionMode > mode) that looks perfect but it is writen in the SDK manual that the > arguments inTime and mode are ignored inside an operator. So I get the > final geom and not at modeling stage. > > So my question : any chance/workaround to get the geometry at stack level > siConstructionModeModeling inside a c++ custom operator ? > > Many thanks > > Rémi >
