KW00001440: Fix plugin library unloading.

When running pvpython, if your Python script loaded some plugins (from
shared libraries) and called "quit" or "exit" in the Python script
itself, pvpython would segfault, if you created a proxy from the plugin.
The problem was arising from the fact that the plugin shared library was
unloaded before the VTK object corresponding to the proxy was destroyed
during ProcessModule singleton cleanup. This was happenining because the
vtkPVPluginLoader cleaner singleton (which unloads libraries) was
finalized before the vtkPVPluginLoader singleton (which cleans up
unreleased proxies).

Fixed by adding a Schwarz counter to ensure that the plugin loader is
not finalized before the process module. Since vtkPVPluginLoader.h is not
included in a large number of translation units (and there's never need
for it), the overhead for this is minimal.

Change-Id: I0db6f4fc4e0657a623cb2dccefbb55a90ec05cab
Quick-n-dirty pass at fixing the depth buffer in parallel.

Here's a first pass at fixing the depth buffer in parallel for
vtkPVRenderViewForAssembly. To further clean this up, we should do the
following:

+ Cleanup API on vtkPVSynchronizedRenderer to provide access to depth
buffer and color buffer
+ Teach vtkPVSynchronizedRenderer to user color and depth buffer from
IceT when available and grab from frame-buffer when not.
+ vtkPVRenderViewForAssembly should then use that API to get the color
and depth buffer (never having to do actual grabs).

This commit exposes internal methods to use for
vtkPVRenderViewForAssembly as a quick hack. We can come back and fix the
API in future.

Change-Id: I4c62e94377750202a43ac6682feb2d72bf17da58
Switch from arrays to maps to preserve array length.

Change-Id: Ia2ab996232c4242766fd162b6cd91f237b224abb
Fixed the logic for missing values.

Change-Id: I824828b8b6e2a33781cd3705ae3121140de9eb37
Clear out the equivpairs every loop so the memory doesn't increase.

Change-Id: I441956a7c70a8d033a3a02248f20150a0734b906
Cleanup the events and deletes.

Change-Id: I30fd4833798d3bfff55a6382b170c5047c2b427b
Manage deletion of arrays more automatically.

Change-Id: I8bb0311400a2f5d5994519eff82b3503ad0135a5
Improve the scroll area size in pqProxyWidgetDialog

The pqProxyWidgetDialog is populated by a pqProxyWidget which can take any
size. Having a simple default size isn't very robust as the dialog is
used at different places with different pqProxyWidget.
To find the dialog size, we display it offscreen so we can resize it after.

Change-Id: I86755cb1ee9c0f0287ed6eb9714c2b0129f81f63
Revert "qt: Disable Qt modules when support is unavailable"

This reverts commit 9ccbad3d0622a693e3de3c0e0033844551361554.

The logic was incorrect. ParaView ensures that these modules are not
enabled when Qt support is disabled. However, if user still manually
enables these modules, it should indeed find Qt and fail appropriately.

Change-Id: I3806e58beff7eba04039c90e05073de86f0e02b6
Nektar: Fix command order in CMakeLists.txt

In Plugins/Nektar/CMakeLists.txt, call cmake_minimum_required() before
project().  Drop the unnecessary calls to both commands in the
ParaViewPlugin subdirectory.

Change-Id: Ie3294961754a7274523c42a90ee246b1f01307a5
Drop use of the CMake LOCATION target property

CMake 3.0 introduced policy CMP0026 to disallow use of the LOCATION
target property.  Drop our unused lookup of the protoc_compiler
LOCATION.  Replace our lookup of the kwProcessXML LOCATION with a direct
reference to the target in the custom command.  CMake will replace
the reference with the location while generating the project.

Change-Id: I78ffa82eb2aa57b30586e3f79102d2dfdaa07666
Drop outdated CMake Policy settings

Drop explicit calls to cmake_policy() to set policies that are already
set by our cmake_minimum_required(VERSION) calls.  Drop our setting of
CMP0017 to OLD because.  It was incorrectly set to OLD to silence a
warning but should have been set to NEW to silence the warning, and that
is now done by our cmake_minimum_required call.

Change-Id: I6cc32dd987510f34defc0d0b03e1925ce557ff4a
Fix bug 14687 (inconsistent label size)

Font sizes were computed for individual color legend labels.
Labels with fewer digits were enlarged to fit in the target
width and height. Changed this to set the font size for all
labels to the smallest computed label font size.

Change-Id: Ibd4daca5c0f42d6fae321850fbefe737a32de313
Made it possible to disable tick marks and labels

Addresses bug 14697.

Labels and ticks were always drawn. This change makes it possible to
not draw them if desired. By default, they are drawn.

Also, created a new "Labels" section in the color legend options
panel for these new options and existing label options.

Made label for "number of labels" option more accurate.

Change-Id: I5b9b833aa8a8be0d96a77fcbbb36c674e1947644
Enable setting the side on which tick marks appear

Addresses parts of bugs 14696 and 14697.

Exposed option to select on which side of the color legend tick marks
appear and in turn annotations (since they are on the side opposite
the ticks).

Change-Id: I1cbb9a789cf434f2e7fcaad9cb88b18d0c1e8b79
Added options to position color legend title

It can now be placed on the left side, right side, or center of the
color bar in the legend.

Change-Id: I1e7a740097ead3475322a70980ed4e6de8020e0f
Fixed placement of title

Change-Id: I152bdbcc599a9f8d735d4996a75db937b65f0e6a
Added NoCustomDefault option to vtkSMProperty

Some properties (such as scalar color legend title)
shouldn't be overridden by the custom defaults mechanism.
Added XML attribute for this option. Added this option to
XML description for the ScalarBarActor proxy XML.

Change-Id: I68dcba7c76e5ada10a8334ce43721954eb759d51
Made adding of range annotations optional

The minimum and maximum were always added to annotations.
Made this optional.

Change-Id: Ib13cd654cfea40a93770526b2c4cb4cf845d4d98
14685: Turned display of min/max values off by default

Change-Id: I74fd71bb1bc3ea630f5052575fc2e8aaa1085c99