[vtk-developers] vtkAreaPicker bug?

[David E DeMarle]

RenderedAreaPicker does not hit the transformed props because it runs
AreaPicker first to limit the number of props it has to consider. It
is supposed to refine the choice that AreaPicker does in case you
select an area in the bounding box that misses the data.

In any case try changing these lines in vtkAreaPicker.cxx, they should
get the bounds from the prop instead of the mapper which will include
the view transformation.

-          mapper->GetBounds(bounds);
+          double *bds = propCandidate->GetBounds();
+          for (int i = 0; i < 6; i++)
+            {
+            bounds[i] = bds[i];
+            }

and

-          imageActor->GetBounds(bounds);
+          double *bds = propCandidate->GetBounds();
+          for (int i = 0; i < 6; i++)
+            {
+            bounds[i] = bds[i];
+            }


On Fri, Jun 20, 2008 at 10:23 AM, David E DeMarle
<dave.demarle at kitware.com> wrote:
> I'll take a look.
>
> On Fri, Jun 20, 2008 at 9:46 AM, hagbard23 <philipp.huebner at freenet.de> wrote:
>>
>> the problem is that it seems like this class cant pick transformed props
>> too????
>> --
>> View this message in context: http://www.nabble.com/vtkAreaPicker-bug--tp17916442p18029925.html
>> Sent from the VTK - Dev mailing list archive at Nabble.com.
>>
>> _______________________________________________
>> vtk-developers mailing list
>> vtk-developers at vtk.org
>> http://www.vtk.org/mailman/listinfo/vtk-developers
>>
>