In ParaView 3.6.2 it appears to be still impossible for a filter to have output extent different than input extent.
Here is a relatively recent post from someone with the same issue. http://markmail.org/message/frmcm2wnce3ye6ae Is there any suggested work-around for this? As a demonstration, I have attached ImageConstantPad.xml, which converts the VTK class vtkImageConstantPad into a ParaView filter. Regardless of how much padding is requested, the output image will be no larger than the input image. Even when the extents are forced, by for example subclassing vtkImageConstantPad and overriding UPDATE_EXTENT before calling vtkImageConstantPad::Request_Data, thus forcing at least vtkImageConstantPad itself to update correctly, subsequent filters in the pipeline still receive the original (incorrect) UPDATE_EXTENT. Eric
ImageConstantPad.xml
Description: XML document
_______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Follow this link to subscribe/unsubscribe: http://www.paraview.org/mailman/listinfo/paraview
