GitLab

ENH: Provide VTK level infrastructure for point selection. There is now a new optional selection render pass which renders every N'th vertex of each polygon in color N. A new query method after the selection render will return two arrays, an 'any vert selected in this cell' array and a 'these particular vertices were the ones selected' array.

ENH:Sped up depth peeling by adding HasTranslucentPolygonalGeometry() and fixed it with volumes by splitting RenderTranslucentGeometry() into RenderTranslucentPolygonalGeometry() and RenderVolumetricGeometry() in all vtkProp(s)

ENH: Add test for vtkVisibleCellSelection and vtkFrustumExtractor. BUG: 1) Allow actor selection to work without having to supply a prop addr to id map by creating one automatically. 2) Fix non selectable actor invisibility. 3) Obey the pickable flag.

COMP: Fix compilation on 64 bit systems. Create a better actor-address to selection-index map that handles 32 or 64 bit addresses cleanly.

BUG: Fix selection for client server mode with IceT. Actor Id lookup is now done before selection rather than after. Instead of looking up the actor addresses in a table after selection, the caller now supplies a lookup table of actor addresses to ids before hand and the ids are used to color with.

BUG: Minor fixes for selection, cell id pass skipping was not working. IceT client server mode was not selecting and it would fail if the background was not black. VTK level selection was not working properly.

BUG: fixed problem with stereo - now we set the LeftEye of the camera from the render window rather than simply toggling it with each render

ENH: Add a flag that enables/disables the rendering.  This allows you to
render only part of or multiplex a render window.

BUG: [backward compat change]. GetActiveCamera() does not reset the camera anymore. If the renderer had no camera, it would create one automatically *and* reset it. This side effect would trigger the whole pipeline to get the props bounds. Moreover, a call to GetActiveCamera()->Foobar() would have different/inconsistent results depending on whether or not the renderer had a camera already. GetActiveCamera() still creates a cam, but does not reset it. If one calls GetActiveCamera(), it should have full control of it anyway at this point (and reset it or not). The old friendly behaviour remains though, if the user does not bother with the camera at all, it is created during the first render *and* reset to show the whole scene.

BUG: (?): GetActiveCamera would instantiate a camera, and call a ResetCamera. This would have a lot of side effects side effects (like computing the bounds of all props, which will eventually call UpdateInformation() on data objects, etc). It's old, but let's try without. Obviously can be solved by calling ResetCamera manually.
    // this->ResetCamera();

ENH: Another windows.h update.  Methods that are mangled are now all deprecated (except GetClassName which will have its own pass later).  Those that were renamed to have internal protected names (like RemovePropInternal) have been renamed again to a new non-mangled public name (like RemoveViewProp).  After the VTK 5.0 release we can remove the mangled names altogether.

ENH: Removing inclusion of windows.h by top VTK headers.  This results in a substantial compile time reduction (~70%) on Windows compilers.  It also avoids forcing windows name mangling on user code.  Preprocessor work-arounds for this mangling has been added for VTK methods.  A new vtkWindows.h has been created for VTK code that really needs the windows API.  A vtkOpenGL.h has been created for VTK code that needs GL/gl.h because this header requires windows.h to be included first on some compilers.  This addresses bug #836.