Add margin in vertical scalar bar between title and bar.

Add a setting to fine tune the distance between the bar and the title.

Change-Id: I64cc824c70126a3854c501cc65335d6421835a75
Update baseline image.

Change-Id: Ie571d417ffdac4c44ead2fbb42080ac03cfc60e5
BUG:11947 plug memory leaks in vtkSelectPolyData exceptions

Thanks Xabi Riobe for the patch.

Change-Id: Ie1fe74a12a67234c752fd02263c6d5df7b759d4b
Removed obsolete vtkCxxRevisionMacro (in comments)

Change-Id: I5c3bf3b9caa0d75eec299633dabf0d21457e982a
Replaced use of deprecated constants

Also wrapped the deprecated ones in VTK_LEGACY_REMOVE

Change-Id: I57545d25853c9594c57bc9c0f5c626f2a9dd36a0
Replaced deprecated constant names with new names

Wrapped old names in VTK_PARSE_LEGACY_REMOVE

Change-Id: If8619ae465943257e8ce99e6d943c26ca1db5499
COMP: Drop extra comment terminator in vtkInteractorForwarder.java

This was added by commit 4e2c8345 (Add CEA support signature in the
copyright information, 2013-08-05).  Remove it.

Change-Id: Id0d0db857db76724b63900e9cc6d2b79c17cfd4f
Merge topic 'Java-Wrap-Add-SWT-work-Copyright-information' into master

607e7178 COMP: Drop extra comment terminator in vtkInteractorForwarder.java
Perform explicit list deletion in CCSEdgeLocator.

The vtkClipClosedSurface helper class vtkEdgeLocatorNode would
delete the whole node list in its destructor.  This is a bad
idea, because because if the implicit copy constructor is called
on a node, and the copy destructs, then the list will partially
destruct.  Add a FreeList() method that is called explicitly when
the list is to be freed.

Change-Id: I8945dc1682b6a70f66561b1f4155ed22be6fb0d6
Add a copy constructor to vtkArrayWeights.

The vtkArrayWeights header declares a destructor, therefore it
must also declare a copy constructor and assignment operator
according to the "rule of three".  In C++11 mode, clang gives
a warning when the "rule of three" is broken.

Change-Id: I0b5041100d5f00cdb0ddd709853ee49b151bba8e
Merge topic 'arrayweights-copy-ctor' into master

e6d1e307 Add a copy constructor to vtkArrayWeights.
Fix problems processing polyhedron connectivity.

Several filters incorrectly process polyhedra because of
misunderstandings of how their connectivity is stored or
simple math errors in computing connectivity offsets.
Fix them.

Change-Id: Icce8becea56567b869277d0d265e3f9092b7eb98
Replaced use of critical section with runtime initialization.

vtkPolyData class uses a class variable that it was initializing
lazily - which required a mutex to do in a thread safe way. Since
mutexes are expensive, I replaced this with a run-time
initialization, which is thread safe and much less expensive.

Change-Id: I34bcee4b4e5f105a00ebd87129a5debff0170705
ENH: Remove superfluous IMMEDIATE option from CMake CONFIGURE_FILE

In CMake 2.0 and higher (since 2005), the IMMEDIATE option to
CONFIGURE_FILE is implicit:
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=c9cc368a

Change-Id: I60e48f767d33e0a364dfc9cafd9821836b2f3f43
Merge topic 'CMake-Immediate' into master

1f965eec ENH: Remove superfluous IMMEDIATE option from CMake CONFIGURE_FILE
Don't forget to copy polyhedron cell-data...

... when appending datasets.

Also, clear out point-list when GetFaceStream fails.

Change-Id: Icf502a95ec8bfacc634291c6ef749d3cbdff5df9
Fix polyhedron-ray intersection...

... by properly resizing point and point-id arrays for
each polygonal face before intersecting with the ray.

Change-Id: I24b7053428e50152c8e10fcb240a56a924e772ce
Reset point ID list when appending polyhedra.

Change-Id: I0d5ef2af0323e57ef08de64235a34f4672f3bb9f
Terminate early when possible.

Change-Id: Ibcd1bb931c4f72960a3c997bf4d84653516d70f4
Reads past EOF are expected

The vtk3DSImporter reports errors like :

ERROR: In /home/kevin/kitware/VTK/IO/Import/vtk3DSImporter.cxx, line
1083
vtk3DSImporter (0x75cd20): Pre-mature end of file in read_word

on almost every machine in the dashboard.

I did a bit of poking around with gdb and std::cerr, and it looks like
these reads past the end of the file are not at all unexpected.

For example parse_face_array uses read_word to read the number of faces
and then to read what I assume are the face vertex ids: a failure here
is catastrophic.

Then even though importer->GetFileFD() could be at the end of the file
it calls start_chunk which calls both read_word and read_dword to see if
there is another (sub?)chunk to parse into.

This commit adds two new functions peek_word and peek_dword that are
exactly like read_word and read_dword except that they do not report an
error when they read past the end of the file.

peek_word and peek_dword replace read_word and read_dword in start_chunk
where the read past the end of the file is not an error.

read_dword is now unused

Because read_dword is now unused, it should be removed.

Stop leaking render windows

Hopefully X and Mesa have advanced to the point where we can delete the
render window without error.

If any tested configurations still have trouble let us work around them
more precisely.

Change-Id: I90a68d1241379886d38d150ba00816d869c6675f