no pick in vtkProp3DButtonRepresentation if window not mapped

Crash when a vtkWidget with a vtkProp3DButtonRepresentation is
enabled before the render window was mapped. The OpenGL context
used when doing picking in ComputeInteractionState was not yet
initialized.

Change-Id: I9791a52606f008a8f607ed803d47321eae4e5522
KWSys: Teach SystemInformation to report more information

Updates to kwsys SystemInformation to support probing of the current processes
memory usage in KB(linux,win,mac), the total physical memory in KB(linux,win,mac),
and to report the model name field of the cpuinfo(linux only). a method to return
the host's FQDN, and methods to test for OS type(Windows, Apple, linux). These
additions/modifications will be used by ParaView's MemoryInspector.

Change-Id: I69cf3d25b27aefca1602d4255412f4d32a75ca27
Speedup vtkCollection::RemoveItem(vtkObject*)

To remove an item from its object, the list was browsed twice:
once in vtkCollection::RemoveItem(vtkObject*) to find the object index and
once in vtkCollection::RemoveItem(int) to remove the element.

Change-Id: I66775509aec36eda435b95bbbe3c94a6aa3ef586
vtkCollection::RemoveItem(int) fired Modified too early

The collection was firing ModifiedEvent before being actually modified.

Change-Id: Ic740f10cfae055691fe5adb9eaaff787592878b9
BUGFIX: Resolve issue with random mode and and setting of max no of pts.

Problem:
 If random mode is on and the maximum number of points has not been set
 then the following error is triggered due to an attempt being made to
 allocate a VTK_LARGE_ID array of points.

 ERROR: In ... vtkDataArrayTemplate.txx, line 144
 vtkFloatArray (00000000026EB980):
 Unable to allocate 9223372036854775805 elements of size 4 bytes.

 The failure is initially caused by this line:
 vtkIdType localMaxPts = this->MaximumNumberOfPoints;
 because numNewPoints has been set to VTK_LARGE_ID

Solution:
 A check has been inserted to ensure that if the maxium
 number of points exceeds the number of points in the input data then
 localMaxPts is clamped to the number of points in the input data.

The underlying assumption is that you cannot
mask more than the total number of points in the input.

Change-Id: Iffbcaacbd493d105df4151d771f2eb9ccc1039ba
Fix a few performance bugs in parallel stream tracing

- terminate trace if a new seed point fails all bounding box tests
- the # of "peeks" should start with 1

Change-Id: Ia65571f92f170c6fc31e91f503bfb6f55161f4e7
Merge topic 'speedup-pstreamtracer' into master

f6e71410 Fix a few performance bugs in parallel stream tracing
Merge topic 'mask_points_array_allocation_failure' into master

68858bd9 BUGFIX: Resolve issue with random mode and and setting of max no of pts.
COMP: Add python version numbers only to files, not to targets.

Adding the python version numbers to the targets for the VTK python
libraries was a mistake, it makes it hard for external packages to
find the library targets in VTKTargets.cmake.  This patch adds the
version numbers only to the library files, not to the target names.

Change-Id: I567fde9e7243f3115c20e21b077f3ce0e708f6fa
A new subclass of vtkCutter that support composites and streaming AMR

vtkCompositeCutter adds the following functionality:
- it loops over all data sets in a composite data set input
- it uses AMR meta information, if availble, to compute intersecting
data sets and only requests those.

There is a also a change in the AMR reader so that meta data can be
generated for partial AMR.

Change-Id: Ifc8f498c2cf56945f899ffa5785e0bc91acdec97
Merge topic 'composite-cutter-with-AMR-streaming-support' into master

bceecd9c A new subclass of vtkCutter that support composites and streaming AMR
Merge topic 'vtk-python-unversioned-targets' into master

1494cdd4 COMP: Add python version numbers only to files, not to targets.
Merge topic 'mem-insp-tree-2' into master

595216ab KWSys: Teach SystemInformation to report more information
COMP: Remove vtkPythonCoreModule.h from vtkPython.h

There is no reason for vtkPython.h to include vtkPythonCoreModule.h.
In the future, vtkPython.h could be moved out of PythonCore altogether,
so that modules can use python as a utility without actually requiring
the python wrappers to be built.

Change-Id: I59d011320c78762cc69807801219c8680caa679b
Move Wrapping/PythonCore to Wrapping/Python

Change-Id: I7c6b95a9299809c308c3656dc9128b43a9a7733c
Fixed bug in determining locator bucket for search point.

There was an inconsistent way of finding which locator bucket
a search point was in. It was different in vtkMergePoints
which derives from vtkPointLocator so I created a method to do
that in vtkPointLocator and used it everywhere it was done.

Change-Id: I11e0923b828bba7bda68a18f1277434656b30c5a
This example works again with recent changes in VTK modularization

Change-Id: I8141c065e9545b7831a6e41216783b76045f2109
Print out information about calculated meshes, contours, cuts, etc.

Change-Id: I342474b9c74cbb3d3a1550f0ee3b2cf950b9ac33
Removed old (VTK5 maybe?) boilerplate code

Change-Id: Icb9d9ba20905a6674a22a6ac1b199bfa87a47770
Auto-adjust contour values to data range

Change-Id: I01a75bce1973fae3291b660c6cbd8bea27f8d9c4