[vtk-developers] Proposed information key UNRESTRICTED_UPDATE_EXTENT

[David Gobbi]

I only plan to use UNRESTRICTED_UPDATE_EXTENT for vtkImageStencilData
sources, for which I know it is safe, but yes, I was also considering
that it could be used by vtkImageData sources somewhere down the road.

Fortunately, the separation of RequestInformation and RequestData
really helps the image algorithms to not make assumptions.
RequestInformation deals with WholeExtent, RequestData deals
with the Extent.  I will look through the existing filters to see if any
RequestData/Execute methods use WholeExtent for anything... those
are the filters that might break.

  David

On Fri, Nov 19, 2010 at 12:32 PM, Berk Geveci <berk.geveci at kitware.com> wrote:
> This concerns me a bit. There may be algorithms that assume that update
> extent and data extent will be equal to or less than the whole extent. What
> happens if one of those is in the pipeline?
> -berk
>
> On Tue, Nov 16, 2010 at 9:28 AM, David Gobbi <david.gobbi at gmail.com> wrote:
>>
>> I've put a patch on gerrit that cleans up some of the VTK stencil code:
>> http://review.source.kitware.com/#change,366
>> The idea is that algorithms can set UNRESTRICTED_UPDATE_EXTENT on any
>> outputs that can be generated for any requested update extent, i.e.
>> neither the update extent or data extent is limited to the whole
>> extent.  My intent is to only use it with vtkImageStencilSource, but
>> it might have other uses.
>>
>>  David
>> _______________________________________________
>> Powered by www.kitware.com
>>
>> Visit other Kitware open-source projects at
>> http://www.kitware.com/opensource/opensource.html
>>
>> Follow this link to subscribe/unsubscribe:
>> http://www.vtk.org/mailman/listinfo/vtk-developers
>>
>
>