it could be connected as an output then, right?
On Fri, Dec 21, 2012 at 11:55 AM, Schoenberger <[email protected]> wrote: > > The data is created the other way. > It is not that my operator needs the data from the property. > The operator creates the mesh and then puts some infos about the mesh into > the property. > > > > > Holger Schoenberger > technical director > The day has 24 hours, if that does not suffice, I will take the night > > > Quoting Luc-Eric Rousseau <[email protected]>: > > if you need anything, you should connect it as an input. Is there s >> problem with that? >> Le 2012-12-21 14:05, "Schoenberger" <[email protected]> a écrit : >> >> Hi >>> >>> >>> I have created a custom operator. >>> In the update function of the COP I get the myobject.polymsh as context. >>> But I need to access a custom property that is attached to myobject. >>> >>> So far I found two functions which usually return the object. >>> CRefArray GetOwners >>> X3DObject GetParent3DObject >>> But both are stated as: >>> "If this function is called from the cb_Operator_Update Update context of >>> a custom operator it returns an empty array" >>> >>> No explanation why. >>> >>> Any hints how to solve this issue? >>> >>> Last chance would be perhaps to hack a little bit. Get the name >>> myobject.polymsh as string, cut the polymsh and use that to create a new >>> X3DObject? >>> >>> >>> Holger Schoenberger >>> technical director >>> The day has 24 hours, if that does not suffice, I will take the night >>> >>> >>> >>> >>> >>> >> > >
