[prev in list] [next in list] [prev in thread] [next in thread] 

List:       paraview
Subject:    Re: [Paraview] vtk data objects as property: how to handle that in
From:       Berk Geveci <berk.geveci () kitware ! com>
Date:       2009-01-30 13:41:37
Message-ID: 45d654b0901300541u7c8b856bg8ee571f614ececd7 () mail ! gmail ! com
[Download RAW message or body]

This sounds like a poor filter design. It sounds like instead of
exposing a filter's properties through public setters and getters, the
developer bundled all of them into one property object. I'd recommend
subclassing this filter to add proper setters and getters and
including the subclass in ParaView as a plugin.

-berk

On Fri, Jan 30, 2009 at 7:24 AM, Jérôme <jerome.velut@gmail.com> wrote:
> Hi,
>
> Some VTK filters, such as vtkImageReslice, have vtkImageData as
> property. This is not really an input, just an object than may give
> information about, for example, spacing, extent, data type, etc.
> What is the property to be used in a paraview XML plugin file ? I
> wondered about ProxyProperty, but I am not sure how to use it in the
> case of vtkImageReslice.
>
> In other words, when a VTK filter has accessor like:
> vtkSetMacro( Information, vtkImageData* );
>
> What is the XML corresponding? Maybe that:
> <ProxyProperty name="Information"
>                         command="SetInformation"
>                          ... >
> When to tell this is an image data ? How the user can give the image
> data to the proxy ? As the InputProperty is linked to the
> vtkAlgorithmOutput type, it cannot be used in this case...
>
>
> Thank you!
>
> Jerome
> _______________________________________________
> ParaView mailing list
> ParaView@paraview.org
> http://www.paraview.org/mailman/listinfo/paraview
>
_______________________________________________
ParaView mailing list
ParaView@paraview.org
http://www.paraview.org/mailman/listinfo/paraview

[prev in list] [next in list] [prev in thread] [next in thread]