[Paraview] ParaView v3.9.0: problems with exporter plug-in

[Nenad Vujicic]

Hello everyone,

Because of Xdmf problems inside of v3.8.1, I tried to use my exporter
plug-in with current v3.9.0 sources. I downloaded sources from Git
repository and compiled them with Visual Studio 2008 SP1, Python 2.7
and OpenMPI 1.4.3. Unfortunately, in exported scene I got only center
of rotation axes and orientation axes.

After closer inspection, I made very short snipped that shows the
problem. In class derived from vtkExporter, in function WriteData() I
override, I call following sequence:

   - for every renderer in RenderWindow
     - for every actor in renderer // only 3d actors
       - mapper = actor.GetMapper()
       - if(mapper != NULL)
         - mappers_input = mapper.GetInput()
         - print mappers_input // PROBLEM: NULL for whatever I add to
pipeline, instead of 2 axes meshes

At the moment, I read 3 renderers, the first renderer has 5 actors (2
for center of rotation axes mesh and 3 LOD actors), the second 0 and
the third has 9 actors (all for orientation axes mesh). The problem is
in 3 LOD actors for which I get vtkCompositePolyDataMapper2 objects as
mappers, but which return NULL on GetInput() always! In v3.8.x I used
same mechanism to get vtkPolyData and other data sets from which I
would later extract scene's properties.

Am I doing something wrong or exporter's part still requires some work
before v3.9.0 is released? Btw, similar occurs when I try to export
scene to VRML - only center of rotation axes mesh is exported.

Thanks,
Nenad.