<div class="gmail_extra">I'm just getting around to looking into this now. I'll let you know if I fix this for my case. On a related note, does there exist a filter which takes as input a specified 2D vtkPolyData, and a set of candidate 2D vtkPolyDatas, and returns a list of those candidate vtkPolyDatas which are wholly inside the specified input? This seems to be related to this filter.<br>
<br><div class="gmail_quote">On Thu, Apr 19, 2012 at 11:03 AM, David Gobbi <span dir="ltr"><<a href="mailto:david.gobbi@gmail.com" target="_blank">david.gobbi@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi Jonathan,<br>
<br>
This is why I haven't added this filter to VTK yet. When the input<br>
has multiple contours, the code doesn't yet have the necessary logic<br>
for determining which contours are holes. In your case, it has<br>
incorrectly marked the large contour as a hole.<br>
<br>
Unfortunately I cannot provide you with a timeline for when I will<br>
finish this filter, lately I've been crazy busy on other projects.<br>
But if you want to give it a shot yourself, take a look at the code<br>
for vtkContourToPolygonFilter::MakePolysFromContours(). The<br>
section that needs to be modified is the block that starts with<br>
"if (normal == 0)".<br>
<span class="HOEnZb"><font color="#888888"><br>
- David<br>
</font></span><div class="im HOEnZb"><br>
<br>
On Thu, Apr 19, 2012 at 11:44 AM, Jonathan Morra <<a href="mailto:jonmorra@gmail.com">jonmorra@gmail.com</a>> wrote:<br>
><br>
> After using your filter for a little while, for the most part it works great, however I have discovered a few cases where it doesn't work. I've attached a screen shot showing a failure, The first image is the input vtkPolyData, and the second is the result of running through your filter. Can you determine what is going on? If not, I'd be happy to give you the poly data I'm using, just let me know how to export it to disk, and I can email it to you.<br>
><br>
> Thanks<br>
><br>
> PS The behavior seems unpredictable, as sometimes with shapes just as complicated it works fine, I can't seem to tell what makes it fail.<br>
><br>
><br>
><br>
><br>
><br>
><br>
</div><div class="HOEnZb"><div class="h5">> On Tue, Apr 10, 2012 at 12:26 PM, David Gobbi <<a href="mailto:david.gobbi@gmail.com">david.gobbi@gmail.com</a>> wrote:<br>
>><br>
>> Use the PickableOff() method (on the actor, not the data).<br>
>><br>
>> On Tue, Apr 10, 2012 at 1:17 PM, Jonathan Morra <<a href="mailto:jonmorra@gmail.com">jonmorra@gmail.com</a>> wrote:<br>
>> > One more question along this same line. Now that I have opaque vtkPolyData,<br>
>> > I'm noticing that my vtkPicker is no longer hitting the same data it was<br>
>> > before, it's hitting the now opaque poly data. This makes sense to me, but<br>
>> > I don't want it to happen. Is there a way to tell the vtkPicker to ignore<br>
>> > some vtkPolyData (ie always pick the underlying data).<br>
>> ><br>
>> > Thanks<br>
><br>
><br>
</div></div></blockquote></div><br></div>