I don't think it is as simple as renaming GetInput() to GetInputData(). There is indeed an asymmetry to the way these classes behave:<div><br></div><div>SetInputData() - sets a data object as input without creating a pipeline a connection to whatever might have produced the data object</div>
<div>SetInputConnection() - sets up a pipeline connection to an algorithm</div><div>GetInput() - returns the input data object that may result from either of the above functions</div><div><br></div><div>So GetInput() does not simply pair with SetInputData(). It's not like SetInputData() sets a data member and GetInput() returns it. This is why I left GetInput() alone.</div>
<div><br></div><div>-berk<br><br><div class="gmail_quote">On Fri, Mar 9, 2012 at 3:04 PM, Marcus D. Hanwell <span dir="ltr"><<a href="mailto:marcus.hanwell@kitware.com">marcus.hanwell@kitware.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi David,<br>
<div class="im"><br>
On Fri, Mar 9, 2012 at 2:18 PM, David Gobbi <<a href="mailto:david.gobbi@gmail.com">david.gobbi@gmail.com</a>> wrote:<br>
> Hi Marcus,<br>
><br>
> There is an asymmetry in the naming of the new SetInputData() method:<br>
><br>
> void SetInputData(vtkDataObject *);<br>
> vtkDataObject *GetInput();<br>
><br>
> Why is it SetInputData(), but just GetInput()? The reason that I'm<br>
> concerned is that some of my wrapping tools require symmetry in the<br>
> naming of Get/Set methods in order to infer class properties.<br>
><br>
</div>That is a good point, and wrapping or no I think it would be good to<br>
restore the symmetry. Berk made the changes, it seems like something<br>
that we could change.<br>
<br>
Thanks,<br>
<br>
Marcus<br>
</blockquote></div><br></div>