[vtkusers] Is it possible to keep the original Ids for picking after vtkClipPolyData?

[David E DeMarle]

And it also sounds like a bug.

Filters that don't know how to trace ancestry across should remove the
ID array, not recompute it.
The rationale is that is alright to produce an "I don't know" answer,
but not alright to produce an incorrect answer.

Can you post a small sample of code which demonstrates the problem?

David E DeMarle
Kitware, Inc.
R&D Engineer
28 Corporate Drive
Clifton Park, NY 12065-8662
Phone: 518-371-3971 x109



On Fri, Apr 29, 2011 at 4:40 PM, David Gobbi <david.gobbi at gmail.com> wrote:
> Hi Hong,
>
> You can avoid this problem by using the mapper to clip the data,
> via the vtkMapper::AddClippingPlane() method, instead of using
> vtkClipPolyData.
>
>  - David
>
>
> On Fri, Apr 29, 2011 at 2:33 PM, Hong Yi <hongyi at renci.org> wrote:
>> Hello,
>>
>>
>>
>> I am using vtkClipPolyData to clip polydata geometry in combination with
>> vtkImplicitPlaneWidget2. It works well but apparently after clipping, the
>> original Ids corresponding to each point (in my case, an atom) in polydata
>> geometry is recomputed. Since I am using the original Ids for picking and
>> highlighting the corresponding residues in another view window, after
>> clipping, the picking and highlighting does not pick the right atom and
>> residue because the Ids are changed after clipping. Is there a way to keep
>> the original Ids after clipping?
>>
>>
>>
>> Thanks for any pointers on this,
>>
>>
>>
>> Hong
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the VTK FAQ at: http://www.vtk.org/Wiki/VTK_FAQ
>
> Follow this link to subscribe/unsubscribe:
> http://www.vtk.org/mailman/listinfo/vtkusers
>