When it comes to images there's whole lot of things to worry about such as extents, extent translators etc etc. Adding support for delivering image data in parallel may not be a trivial task.
Utkarsh On Mon, Dec 29, 2008 at 1:04 PM, jonathan grimm <flym...@gmail.com> wrote: > Can I write a strategy to make it support 3D Image data? > Would a vtkImageDataStreamer solve this problem? > > On Mon, Dec 22, 2008 at 10:05 AM, Utkarsh Ayachit > <utkarsh.ayac...@kitware.com> wrote: >> >> Look at vtkSMClientDeliveryStrategyProxy::UpdatePipelineInternal() >> that's where the data type is set on the data-transfer filter. BTW, >> ClientDeliverRepresentation cannot deliver 3D image data. It can only >> deliver 2D slices. >> >> Utkarsh >> >> On Mon, Dec 22, 2008 at 12:17 PM, jonathan grimm <flym...@gmail.com> >> wrote: >> > How does the ClientDeliveryRepresentation choose what data type to send? >> > I have two pipelines: >> > Reader->ImageReslice->ClientDeliveryRepresentation->ImagePlaneWidget >> > and >> > Reader->ClientDeliveryRepresentation->hacked ImagePlaneWidget that >> > allows >> > pipeline inputs >> > The first works beautifully, while the ImageReslice inside my second >> > pipeline complains that it is getting polydata instead of imagedata. >> > Any suggestions, besides producing an image plane widget that uses a >> > server >> > side reslice? >> > >> > -- >> > Sometimes it's hard to tell the dancer from the dance - Corwin in CoC >> > >> > _______________________________________________ >> > ParaView mailing list >> > ParaView@paraview.org >> > http://www.paraview.org/mailman/listinfo/paraview >> > >> > > > > > -- > Sometimes it's hard to tell the dancer from the dance - Corwin in CoC > _______________________________________________ ParaView mailing list ParaView@paraview.org http://www.paraview.org/mailman/listinfo/paraview
