Proposal to change double click event vtk mapping

[Davide_Punzo]

@dcthomp

@Davide_Punzo The change you suggest might be better than nothing, but it feels like it could also cause problems should an application be listening for single-click events. Without at least updating the RepeatCount to 1 before invoking vtkCommand::xxxButtonPressEvent , this seems problematic.

The repeatCount is equal to 1 when the vtkCommand::xxxButtonPressEvent is fired in the if condition QEvent::MouseButtonDblClick in the temp solution (I really didn’t undestrand why and where it gets update to 1), so one can distinguish vtkCommand::xxxButtonPressEvent from single and double clicks.

But again, I agree with you and I don’t like the temp solution: it’s dirty and would confuse developers to have two double clicks events “systems”. I would prefer to have just vtkCommand::xxxButtonDoubleClickEvent at QEvent::MouseButtonDblClick events (current status) and remove the repeatCount ivar along VTK (by updating it where necessary). On the other hand, I don’t have time to address this properly now, and the temp solution may help with the transition.

@dcthomp

I’ve merged my change, which simply ensures that double-click events are passed to interactor styles and updates one subclass ( vtkContextInteractorStyle ) to pay attention to them.

great, thanks!