[vtkusers] Selection with vtkCompositePolyDataMapper2 mapper problem
alexmalvtk at gmail.com
Tue Jul 14 00:56:46 EDT 2015
I tried to debug selection and found that in :
vtkSelection* vtkHardwareSelector::GenerateSelection( unsigned int x1,
unsigned int y1,
unsigned int x2, unsigned int y2)
GetPixelInformation(pos, 0); already returns PixelInformation.CompositeID
for block which is outside selection frame as a valid
This means that problem is either within CaptureBuffers() or
and possibly involves painter or mapper.
I afraid I will have to give up on this unless I get any suggestion which
may help me in finding bug location.
On Mon, Jul 13, 2015 at 5:50 PM, Alex Malyushytskyy <alexmalvtk at gmail.com>
> Attempt to upgrade to vtk-6-2-0 did not fix the problem
> On Fri, Jul 10, 2015 at 10:26 PM, Alex Malyushytskyy <alexmalvtk at gmail.com
> > wrote:
>> Using vtkHardwareSelector with vtkMultiBlockDataSet and vtkCompositePolyDataMapper2
>> sometimes is producing wrong results.
>> I have a vtkMultiBlockDataSet with polydata (sometimes NULL) as blocks.
>> On the screenshot you can see the simplest geometry which I can
>> reproduce the problem on. Each rectangle there is a separate block.
>> It also displays window frame which supposed to define selection.
>> As you can see results (in red like colors) There is an extra block
>> selected which is totally outside of the frame.
>> Relative functions which do selection and extraction are available in
>> the attachment.
>> For some reason if I select a single component - basically by clicking
>> without dragging selection frame, result is always correct.
>> Result seems also depends on view angle.
>> I tracked that wrong results appear after vtkConvertSelection::ToSelectionType
>> in converted to vtkSelectionNode::BLOCKS
>> I would appreciate any help or ideas.
>> I am using vtk-6-1-0.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the vtkusers