Proxy property not generating in client server wrapper source

Hi there!

I made a filter called MainProxy.cxx with the following xml:

<ProxyProperty name="ProxyExample"
               command="SetProxyExample"
               label="Proxy Example">
     <ProxyListDomain name="proxy_list">
          <Proxy group="proxy_examples"
               name="ProxyExample1" />
          <Proxy group="proxy_examples"
               name="ProxyExample2" />
     </ProxyListDomain>
</ProxyProperty>

but the client-server wrapper does not generate the associated code in the MainProxyClientServer.cxx. I made sure to follow the logic of the Kernel setup in the PointInterpolator.

If I edit the MainProxyClientServer.cxx and add this piece of code:

if (!strcmp("SetProxyExample", method) && msg.GetNumberOfArguments(0) == 3)
{
    AbstractProxyExample* temp0;
    if (vtkClientServerStreamGetArgumentObject(msg, 0, 2, &temp0, "AbstractProxyExample"))
    {
        op->SetProxyExample(temp0);
        return 1;
    }
}
if (!strcmp("GetProxyExample", method) && msg.GetNumberOfArguments(0) == 2)
{
    AbstractProxyExample* temp20;
    {
        temp20 = (op)->GetProxyExample();
        resultStream.Reset();
        resultStream << vtkClientServerStream::Reply << (vtkObjectBase*)temp20 << vtkClientServerStream::End;
        return 1;
    }
}

everything works, but it dissapears after compilation. ProxyExample1 and ProxyExample2 are children of AbstractProxyExample.

Any hints on why this could happen? Do I have to include more information?

Thank you,
Patrick Laurin

Can you try renaming the classes with a vtk... prefix? I don’t recall if that’s still the case, but a long time ago I remember these classes needed to have a vtk... prefix for the wrappers to treat them correctly.

Maybe an export problem.

I had these kind of issue with improperly exported classes.

Thank you for your prompt response! Indeed, by adding “vtk” in front of my class name, it generates my client server wrapper correctly.

Thanks,

Patrick Laurin