On Wed, Dec 1, 2010 at 11:13 AM, David Doria <span dir="ltr"><<a href="mailto:daviddoria@gmail.com">daviddoria@gmail.com</a>></span> wrote:<div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">
<br>
</div>Here you go:<br>
<a href="http://public.kitware.com/Bug/view.php?id=11550" target="_blank">http://public.kitware.com/Bug/view.php?id=11550</a><br>
<br>
That'd be great, thanks.<br>
<br>
While you add it, can you add a FindCell(double[3]) convenience function?<br>
<br>
The interface is crazy if all you want is the cell id.<br>
<br>
int vtkImageData::FindCell(double p[3])<br>
<div class="im">{<br>
int subId;<br>
double pcoords[3] = {0,0,0};<br>
double weights[8];<br>
</div> return image->FindCell(p, NULL, 0, epsilon, subId, pcoords, weights);<br>
}</blockquote><div><br></div><div>The FindCell() method is part of the abstract interface for vtkDataSet,</div><div>so you shouldn't add a FindCell methods that only applies to a specific</div><div>kind of data set.</div>
<div><br></div><div>I'm not saying that that VTK's data interface is ideal. It could definitely</div><div>stand some improvement. But it has to be improved holistically. So</div><div>any time you ask to add one specific method for one specific data set,</div>
<div>I'll always be on the "no" side. If someone was to put forth a proposal</div><div>to globally improve VTK's data interface, I'd be much more amenable.</div><div><br></div><div> David</div></div>