http://www.vtk.org/Bug/view.php?id=15708

Convert double-quote includes to angle brackets:

 git grep -l '#include "sstream"' | xargs sed -i 's/"sstream"/<sstream>/'

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.

In the early days of VTK, support for stl was not portable. vtksys_stl
and vtksys_ios provided a portable implementation of the stl. Now, all
of the VTK supported compilers have portable stl implementations.

This patch:
  1) Replaces the vtksys_ios:: with std::.
  2) Replaces the vtksys_stl:: with std::.
  3) Removes "using" statements for stl

This is a common issue, worth notifying devs when something is amiss.

...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.

There were a couple spots that were calculating unused values. Moved them
to only be calculated when needed.

Users need an ability to add plots to a Chart but not have it show up in
the legend. This commit adds support for that. This is needed to address
the features requested in BUG #15512.

Fixed ['vtkPlotArea::vtkTableCache' has a field
'vtkPlotArea::vtkTableCache::SortedPoints' whose type uses the anonymous
namespace] warning.

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.

Remove all code marked with VTK_LEGACY...
from before vtk-6.1 (2014-01-21)

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

Fixed all clang -Wimplicit-fallthrough warnings:
- Some fixed by adding missing breaks
- Other fixed by adding VTK_FALLTHROUGH statement

Under (modern) clang with C++11:
 #define VTK_FALLTHROUGH [[clang::fallthrough]]

Otherwise:
 #define VTK_FALLTHROUGH ((void)0)

VTK_FALLTHROUGH serves two purposes:
 - under clang, suppresses -Wimplicit-fallthrough warnings
 - makes code more self-documenting

This was sometimes happening in vtkChart::SELECTION_COLUMNS mode.

It shall not crash when no input is given to the histogram plot.

If off, it prevents the plot from being selected.

A point list can define a poly line or multiple line segments when points
are grouped in pairs.

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

Change-Id: I2d81fe807e22d50913a57fa63c934deadc8e0787

Fixes cppcheck warning, should be a little faster

Change-Id: I24ebe2085e2f1c771d2a83fba6ebfb8761cfb9ab

Sometimes vtkPlotPoints is not added as a plot into a chart.
This is the case vtkPlotFunctionalBag. Therefore when calling Update(),
there can be no Axis.

Change-Id: I5ccd256173831e31b048b732a6021286266e530f

Fix regression from 520548c7

Change-Id: I79c8169b348d211f9abc109768c6586a79a9b911

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