[Paraview-developers] Information meta-data not being passed to representation

[Biddiscombe, John A.]

Please ignore that question. The input information to the view request was not the same as the information from the pipeline itself. I did a bad copy paste from my old code and now I have resolved the problem

JB

From: <Biddiscombe>, cscs <biddisco at cscs.ch<mailto:biddisco at cscs.ch>>
Date: Monday 2 March 2015 13:24
To: ParaView Developers <paraview-developers at paraview.org<mailto:paraview-developers at paraview.org>>
Subject: [Paraview-developers] Information meta-data not being passed to representation

Trying to get my custom representation working with pv-master branch – I’m having some trouble.

The Zoltan partitioning filter add the KdTree to the output information as a metadata key.
(Previously, the extent translator was passed downstream) and in the representation, the KdTree is used to bypass the redistribution step in the compositing code. However, I am not receiving the KdTree in the representation (which is a subclass of vtkGeometryRepresentation).
I can see that my custom information key is passed into pvPostFilter and also in one of the selection filters, but then it gets lost.

There have been some changes in the information key passing in the pipeline – is there anything I should be looking for to see why my key is being thrown away (it does copy itself in CopyDefaultInformation)?

Thanks

JB
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20150302/86f24b0f/attachment.html>