[vtk-developers] vtkGenericRenderWindowInteractor

[Michael Halle]

I think the Interactor stuff as been a great mechanism.  Here's my
only concern, and maybe it's because I haven't thought about it too 
much.

The way the Interactors are called now, they pass on "raw" events:
mouse clicks, key presses, etc. are passed down to Widgets.  That's
the place that's least configurable, because it's compiled in to C++.
Since VTK seems to mostly about "mechanism," not "policy," that seems
like a potential limitation.  It means that bindings, as Prabhu says,
are mostly "all or nothing" with regard to events.  It also means that
if you'd like to have another input device work with a widget, you've
got to map the device's events onto the traditional keyboard mouse
model.

Is there an opportunity for an additional level of indirection, to map
toolkit events to underlying semantic method calls?

Michael Halle
mhalle at bwh.harvard.edu