[Paraview] can vtkImplicitPlaneWidget be used in an XML-only paraview plug-in?

[Dr. Roman Grothausmann]

Dear Utkarsh,


Finally, after visiting the paraview workshop in Lyon, I got my own paraview 
plugin based on c++ for this old task to compile and link. However, already when 
loading it as a module in paraview, paraview crashes with a symbol lookup error:

/opt/paraview-4.1.0_debug/bin/paraview
/opt/paraview-4.1.0_debug/lib/paraview-4.1/paraview: symbol lookup error: 
/net/home/grothama/vtk/paraview_plugins/image-clipper/build/libmyImageClipper.so: undefined 
symbol: _Z19myImageClipper_InitP26vtkClientServerInterpreter

What could be the problem for this? How can I debug this problem?
I tried to combine things from 
ParaViewCore/VTKExtensions/Default/vtkPVMetaSliceDataSet.cxx and from Your XML 
to use a vtkImplicitFunction as an input to a filter.  I had to copy

cp ParaView-v4.1.0/VTK/Imaging/Stencil/*.h 
ParaView-v4.1.0/build_141124/VTK/Imaging/Stencil/

and to add
CMAKE_CXX_FLAGS   -I ParaView-v4.1.0/build_141124/VTK/Imaging/Stencil/

for vtkImplicitFunctionToImageStencil.h to be found by cmake. However, the error 
does not seem to be caused by the stencil stuff. Attached are the files.

Thanks for any help or hints
Roman


On 26/08/13 15:06, Utkarsh Ayachit wrote:
>> Many thanks for Your reply, Your effort to create an XML-plugin and the bug
>> report. Would it help to compile paraview from source with
>> Module_vtkImagingStencil set to ON on our own platform for testing or is
>> there some code adjustment of paraview necessary to allow that?
>
> No, it won't help. I did exactly that an ran into issues with
> vtkImageStencil and ParaView. Evidently, we hadn't tried to use that
> data-object in ParaView before.
>
>> I guess it would not help to specify the location of a separately compiled vtk-5.10?
>
> You are correct, it will not help. We need to track the issue down on
> the ParaView side first.
>
>> Do I understand correctly that with using port_index= You specify which
>> output should go to which input?
>
> That is correct. If not specified, 0 is assumed.
>
>> What is calling e.g. the vtkImplicitPlaneWidget to get the interaction
>> widget for specifying the implicit function parameters?
>
> In this case, it's the "ProxyListDomain" associated with the
> "ImplicitFunction" property. The domain refers to proxies viz.
> ("implicit_functions", "Plane"), etc. If you look at the xml
> definitions for the same in ParaView
> (ParaViewCore/ServerManager/SMApplication/Resources/utilities.xml),
> you'll see that it provides a "<Hints>" section that suggests a
> "PropertyGroup" of type "Plane". That's what's causing the GUI to show
> the vtkImplicitPlaneWidget to control the Origin and Normal
> properties.
>
> Hope that clarifies things a bit.
>
> Utkarsh
>

-- 
Dr. Roman Grothausmann

Tomographie und Digitale Bildverarbeitung
Tomography and Digital Image Analysis

Institut für Funktionelle und Angewandte Anatomie, OE 4120
Medizinische Hochschule Hannover
Carl-Neuberg-Str. 1
D-30625 Hannover

Tel. +49 511 532-9574
-------------- next part --------------
# This exercise demonstrates a filter plugin.
cmake_minimum_required(VERSION 2.6)
  
FIND_PACKAGE(ParaView REQUIRED)
INCLUDE(${PARAVIEW_USE_FILE})

# Use the PLUGIN macro to create a plugin.
ADD_PARAVIEW_PLUGIN(myImageClipper "1.0"
   SERVER_MANAGER_SOURCES myImageClipper.cxx
   SERVER_MANAGER_XML myImageClipper.xml)

-------------- next part --------------
A non-text attachment was scrubbed...
Name: myImageClipper.cxx
Type: text/x-c++src
Size: 4138 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20141211/9b856bcd/attachment.cxx>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: myImageClipper.h
Type: text/x-chdr
Size: 1340 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20141211/9b856bcd/attachment.h>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: myImageClipper.xml
Type: text/xml
Size: 1820 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20141211/9b856bcd/attachment.xml>