[vtk-developers] vtkGenericRenderWindowInteractor

[Bill Hoffman]

At 11:34 PM 4/12/2002 +0530, Prabhu Ramachandran wrote:
>hi,
>
>I just got the the Python-Tkinter widget working satisfactorily.  I am
>not going to change the existing classes (vtkTkRenderWidget etc.) and
>instead plan on adding a new set of classes that use the new
>vtkGenericWindowInteractor.  This is because moving the old widgets to
>the GenericRenderWindowInteractor will break backwards compatibility.

Sounds good, glad to here it is working.   I would say that we should break
backwards compatibility.   It will be better to have only one type
of interaction supported.   We could simulate the old one with a style couldn't
we?

>There are a few questions I have before I go ahead and commit the
>code.
>
> (1) The name of the new classes.  Right now I am thinking of the
> following
>
>     GtkVTKRenderWindowInteractor.py
>
>     vtkTkRenderWindowInteractor.py
>
>     wxVTKRenderWindowInteractor.py
>
> This is consistent with the existing widgets.  Is this OK?
>
> (2) The vtkXRenderWindowInteractor require the use of an Initialize
> and Start call.  However this is not necessary with the
> vtkGenericRenderWindowInteractor.  Also, SetEnabled has no effect
> whatsoever.  The reason is that the code in
> vtkGenericRenderWindowInteractor does not check for Enabled before it
> invokes the events.  Is this the way it is supposed to be or is this
> a bug?  I'd like to know what the correct behaviour is.

That is a bug, I will fix it.  I guess I should also add an Initialize event
that can be used to initialize the vtkGenericRenderWindowInteractor.

It would then be something like this:
vtkGenericRenderWindowInteractor iren
iren AddObserver InitializeEvent SetUpBindings
iren Start

proc SetUpBindings {}{
...
}


>Thanks!
>prabhu
>
>p.s. Sorry about replying to the vtkusers list the last time round.

I think I was the one that started that thread....


-Bill