Kitware Robot authored May 14, 2018 and Brad King committed May 18, 2018

Populate a script with `map_<md5>=<sha512>` variable settings and
then run the following to convert the content link files:

    git ls-files -- '*.md5' | while read f; do
      md5="$(cat "$f")"
      sha512="$(eval echo \${map_$md5})"
      rm "$f"
      echo $sha512 > ${f%.md5}.sha512
    done

This fixes an issue with BadPoints hiding other points
Fix #17687

This redesign the algorithm so it is more consise
This also add a test and update a faulty baseline

The OpenGL2 backend has changed how text is positioned -- instead of
aligning the entire texture manually (and only for rotations that are
multiples of 90 degrees), we now use the anchor position provided by
the text renderer that aligns to the drawn pixels and supports arbitrary
rotations.

Bill Lorensen authored Oct 01, 2016 and Michael Fogleman committed Oct 17, 2016

PlotBox expects a table that contains exactly 5 rows per column. This
patch adds an ErrorMacro with a descriptive message if the table is
not valid.

A new test checks the new error message and uses vtkComputeQuartiles
to create a valid table.

ERR: ChartBox was not displaying the chart title.

PlotBox expects a table that contains exactly 5 rows per column. This
patch adds an ErrorMacro with a descriptive message if the table is
not valid.

A new test checks the new error message and uses vtkComputeQuartiles
to create a valid table.

ERR: ChartBox was not displaying the chart title.

This commits fixes !16836, where bigChart resize
was actually not correctly computed, by painting
once, resizing then triggering a second paint.
It also update baseline for the associated test.

vtkChartMatrix now features a SetSpecificResize allowing to move
the bottom left point of a single chart. This feature is used in
vtkScatterPlotMatrix to move the Big Chart plot a little on top right
in order to prevent overlap, using painter to compute axis bounding rect.
It also add a compare operator to vector in order to use it in the stl.

The OpenGL2 backend does not define a vtkOpenGL2ContextDevice2D class,
so this test will not run when built with OpenGL2. Change it to run if
OpenGL2 is enabled as the OpenGL2 backend requires higher than OpenGL
version 2 OR if the OpenGL1 backend is enabled but Open GL version 2
is available.

Added alternate baseline for TestScalarsToColors output to
accommodate minor differences in OpenGL2 backend.

Kitware Robot authored Mar 08, 2016 and Dan Lipsa committed Mar 08, 2016

Code extracted from:

    https://gitlab.kitware.com/third-party/proj.git

at commit 41bdf05361007f8c5186f3df9944d86bb273ed13 (for/vtk).

Off by default, this new option adds labels at the ends of the axis
with the range values. A separate printf-style format string can be
specified for these labels. If a tick label overlaps one of the range
labels, it will not be displayed.

Modified TestAxes and its baseline to exercise this new option.

1. Fix the "mosaic" bug, due to transform be rewriten
2. Fix a bug concerning the mtime of the scene
3. Adaptating tick size to the scene scaling
4. Updating baseline

This fix is in reference to bug report 0015325. The formula for width now
avoids a conversion from int to double back to int, and bounds are correctly
computed. TestHistogram2D and its resultant image have also been updated to
more closely match the original test image.

...rather than anisotropic scaling, since we can't render fonts like that
anyway.

Now vtkAxis will show the same number of ticks and the
same relative text size when magnifying the image. Text
will still be a little funky if the scaling is anisotropic,
but at the moment our freetype engine doesn't support
anisotropic dpi (not sure if the MPL backend can or not).

New API: vtkContextScene::GetLogicalTileScale() returns
the renderwindow tilescale or (1, 1) depending on whether
ScaleTiles is enabled.

There are some random fixes where vtkAxis objects were being
used without a scene, which led to segfaults when trying to
look up the tile scale internally.

The numbers of digits in the exponent for a float printed
in scientific notation is undefined. We get 2 or 3 digits on
different platforms.

Adding a new plot to plot a region named, vtkPlotArea. This can be used
to plot a region enclosed between two series.

Also added a new test, TestAreaPlot, to test this new plot.

Plots may do extra work when axis' Mtime changes. Don't change its Mtime
unless absolutely needed.

OpenGL 3.2 does not support line width greater than 1 although
many drivers do support it. This adds valid images for cases
where line width is greater than 1.0

Also minor VisualStudio error check

Also a few tweaks to get closer to OpenGL 32 support
for mesa.

TestChartXYZ test fails on various platforms.  It turns out it is
failing due to floating point issues. Basically

1)	By default the plot data points define the bounds of the axes
    for the chart
2)	the axes define the plot area (clip stuff outside that)
3)	which defines the clipping plane equations
4)	which can in turn clip the original data points subject to
    floating point precision

This is what is happening (FYI, the point that disappears in the middle
is actual on the boundary in the depth axis). This patch
“fixes” the test by defining axes that are slightly bigger than the
data and replacing the valid image.

Change-Id: I25e7f05736f274ffc16633d8110767b9a5a5907b

Change-Id: I6512c3c8cc441464ec5d093dca9852f1a30acb6b

Convenience methods are exposed for plots in vtkChartXY

Change-Id: Iccccc18011b74314af3fcd1474ac792a15627ceb