[vtk-developers] Changes to vtkRenderViewBase && derived classes - interactors and render windows

[Marcus D. Hanwell]

Yes, vtkRenderViewBase has never been in a release, and we made the choice to move that API back to vtkRenderView. This is what I was talking about with the interaction mode logic moving to the derived classes. What was there was not very general (rubber band 2D/3D only covers a small set of possible interactors).

I wonder if a general vtkRenderView3D (or similar) might be appropriate, with the appropriate interaction modes in the API. This example could include and set the style that is intended.

Marcus

On Oct 9, 2010, at 8:11 AM, Bill Lorensen wrote:

> I think these compile errors in the wiki examples appeared after your checkin?
> http://www.cdash.org/CDash/viewBuildError.php?buildid=743153
> 
> Here is the code:
> http://gitorious.org/vtkwikiexamples/wikiexamples/blobs/master/Cxx/Views/RenderViewBase.cxx
> 
> Bill
> 
> On Thu, Oct 7, 2010 at 11:18 AM, Marcus D. Hanwell
> <marcus.hanwell at kitware.com> wrote:
>> Hi,
>> I wanted to let you know that I just merged a small topic branch that
>> changes the behavior of vtkRenderViewBase (and the derived vtkRenderView,
>> vtkContextView, etc). This is the result of some time Utkarsh and I spent
>> looking at the window popping out problem yesterday afternoon, and I am
>> pleased to report that you can now set the window and interactor in whatever
>> order you want!
>> I would appreciate feedback from any users of these classes, especially if
>> it broke any existing behavior. In order to get interaction working
>> correctly with a QVTKWidget it is still necessary to set window/interactor,
>> but the sequence is no longer important. A simple view invocation in the
>> tests still works as expected, but we have shifted responsibility for
>> instantiating an interactor style to the subclasses.
>> This does raise the question of whether a vtkRenderView3D, or something
>> general like that might be appropriate. It would be quite similar to the
>> vtkContextView, but would set up more appropriate interactors for a general
>> 3D scene, possibly with an enum as in the vtkRenderView case. Lots of thanks
>> to Utkarsh and Jeff Baumes for working on this with me - I think we have a
>> good general solution now.
>> Marcus
>> --
>> Marcus D. Hanwell, Ph.D.
>> R&D Engineer, Kitware Inc.
>> (518) 881-4937
>> 
>> _______________________________________________
>> Powered by www.kitware.com
>> 
>> Visit other Kitware open-source projects at
>> http://www.kitware.com/opensource/opensource.html
>> 
>> Follow this link to subscribe/unsubscribe:
>> http://www.vtk.org/mailman/listinfo/vtk-developers
>> 
>> 
>>