The behavior of the selection has been simplify in the
vtkChartParallelCoordinates. By default, we support only a single
selection like in vtk 9.1.0. Multiple Selection still be possible in
other selection mode like SELECTION_ADDITION and SELECTION_SUBTRACTION.

- The 2D plots would unnecessarily invoke draw commands during each animation frame even though no data points were modified.
- With this commit, only the 3D chart gets redrawn for animations.
- Moved 3D chart into a separate context actor with it's own renderer.
- The main renderer is asked not to erase contents during the start of animation.
- During animation, the 3D renderer is carefully placed such that it's viewport takes up the previous 2D chart's space.
- After animation, the 3D renderer is removed from the window and the main renderer is asked to erase contents before drawing.

- allows derived context items to clean up cache entries which they create in the ::Paint method.

- use cached VBOs to skip unnecessary upload of selected points for subsequent frames.

- this method can be used in both vtkPlotPoints and vtkPlotPoints3D to
 obtain selected points from a bunch of selection indices and points.

- use cached overload of DrawMarkers.
- if there are bad points, it will resort to sub-optimal framerate because it uses raw pointers.

- use cached draw functions.
- use vtkPoints instead of std::vector<vtkVector3f> because vtkPoints gives a vtkDataArray, whose MTime can help cache VBOs.

The legend can be optionally inlined but
its position is always the top right corner.

Add ACTION_TYPES_COUNT in charts valid action types enum.
Needed in ParaView for adding a "Clear selection" action in chart views.

ContainsPoint() requires a 3D point.

Thomas Galland authored 2 years ago and Julien Schueller committed 2 years ago

The 3D chart in the vtkScatterPlotMatrix is now displaying its content correctly when rotating from right to left or down to up.
Fixes also a minor display bug at the beginning of the animation caused by the initial 3D chart's angle that wasn't properly defined.

For modules in Accelerators, Charts, Web, Domains, Geovis, Parallel

* Properly set vtkContextMouseEvent.ScenePos and use these scene coordinates instead of screen coordinates in the Charts API.
* Use Scene size instead of RenderWindow size throughout the Charts API.

This will allow the wheels to use the VTK test suite to validate
themselves.

The 3D chart in the vtkScatterPlotMatrix is now displaying its content correctly when rotating from right to left or down to up.
Fixes also a minor display bug at the beginning of the animation caused by the initial 3D chart's angle that wasn't properly defined.

Found via `codespell -q 3 -S ./.git,./ThirdParty,./Utilities/MetaIO,./Utilities/KWSys -L acount,aline,alledges,ans,ba,childs,co-ordinates,contrl,datas,dota,eiter,inout,inouts,lod,lsit,nin,nd,normale,normaly,ot,outout,pard,pres,siz,statics`

Also remove old nullptr assignments as they are unnecessary
when using vtkSmartPointer.

This is a UNIX only test.

VTK_ABI_NAMESPACE_{BEGIN,END} macro is inserted around all VTK symbols.

Exclusions:
 * C interfaces, such as GetVTKVersion and the python module.
 * third-party libraries and external libraries that are not maintained
   by VTK but are part of the VTK repository.
 * Cxx module tests
 * Utilities
 * Wrapping/Tools

Found via `codespell`

Once upon a time, vtkMath::Pi was float, not double.

Cleanup some adjacent usage of vtkMath::Pi to also change float -> double.

No interface changes.

This is in preparation for deprecation of the implicit conversion from
`vtkStdString` to `const char*`.

This ended up using the `const char*` conversion. Since it is a
`std::string` at heart, this is always non-`nullptr` and therefore true.
Simplify conditions to take this into account.