[vtk-developers] RE: vtkAlgorithm suggestion

[Brad King]

On Tue, 9 Mar 2004, Miller, James V (Research) wrote:

> I wouldn't think speed would be an issue.  It's not like you set/get
> inputs and outputs in an inner loop.

I meant speed of coding the implementation.

> I imagine the issue with typos (people mispelling a input/output) still
> exists with indices. You also have to be careful with indices in
> vtkProcessObject because a user could call
> vtkProcessObject::SqueezeInputArray()
> which could, for instance, "move" input #3 to be input #2.

Typos will not be a problem if filters adopt this suggestion:

> -----Original Message-----
> From: Brad King [mailto:brad.king at kitware.com]
> Sent: Tuesday, March 09, 2004 10:45 AM
> To: Miller, James V (Research)
> Cc: Vtk Developers (E-mail)
> Subject: Re: vtkAlgorithm suggestion
[snip]
> someAlgorithm->SetGradientInputConnection(
>    someOtherAlgorithm->GetGradientOutputPort());

There is no longer going to be such a method as SqueezeInputArray.  Input
ports support zero or more inputs connected simultaneously.  Having many
inputs connected to one input port will take the place of the AddInput
method.

-Brad