View Issue Details [ Jump to Notes ] [ Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0015828VTK(No Category)public2015-11-07 06:002016-08-12 09:55
ReporterPengLi 
Assigned ToKitware Robot 
PriorityhighSeverityminorReproducibilityhave not tried
StatusclosedResolutionmoved 
PlatformOSOS Version
Product Version6.2.0 
Target VersionFixed in Version 
Summary0015828: vtkButtonWidget(with vtkTex) cannot capture correct event/render at correct position when the window has more than one renderers
Description1. create window
2. add two renderers to the window. one is up, one is donw
3. add vtkButtonWidget to the window.
4. When click on the window, move the button to that position (on upper renderer)
  Set current render as upper render.
  capture the position
    int x = this->Interactor->GetEventPosition()[0];
    int y = this->Interactor->GetEventPosition()[1];
  calculate bounds and put the widget
        button->GetRepresentation()->PlaceWidget(bounds);

   Now you have two option.
   1) use input x,y input
   2) calculate the x,y position according to the view port of renderer. Assume you put on the upper render, whose lowerleft maybe (0, 1/2 size of window)
        
5. Do render now. for case
   1), the button will not put on correct position but to top of the window. Seems the position is calculated using (0,0) as lowerLeft
   for case 2) the display is correct

6. Move your mouse to the button
   Nothing happens. You cannot click the button and raise any event

   I debug into vtkTexturedButtonRepresentation2D, it will check the positin of mouse and see if it in area of texture image of the button.
   For case 2, seems the button assume the origin point is (0, 1/2 the size of window height). But the input of MoveAction use display coordination (assume the origin point is (0,0). So it not works
   If you move the mouse down to lower. Example, the button at (20,60), the window size is (100,100), you move to (20, 10),the mouse changed and it think we are on the button. Actually not.

7. So, shall we change the renderer logic? or change the MoveAction/SelectAction logic? at least one is incorrect. I assume the render logic has something wrong.







TagsNo tags attached.
ProjectKitware
Typeincorrect functionality
Attached Files

 Relationships

  Notes
(0035436)
PengLi (reporter)
2015-11-07 06:02

 Use vtkTexturedButtonRepresentation2D for representation in this report
(0037430)
Kitware Robot (administrator)
2016-08-12 09:55

 Resolving issue as `moved`.

This issue tracker is no longer used. Further discussion of this issue may take place in the current VTK Issues page linked in the banner at the top of this page.

 Issue History
Date Modified Username Field Change
2015-11-07 06:00 PengLi New Issue
2015-11-07 06:02 PengLi Note Added: 0035436
2016-08-12 09:55 Kitware Robot Note Added: 0037430
2016-08-12 09:55 Kitware Robot Status backlog => closed
2016-08-12 09:55 Kitware Robot Resolution open => moved
2016-08-12 09:55 Kitware Robot Assigned To => Kitware Robot

Copyright © 2000 - 2018 MantisBT Team