GitLab

The netcdfcxx option isn't important or modified often enough to
warrant top billing.

Also make a note that vtk's findhdf4 is unimportant so no dev wastes
time on it in the future.

Change-Id: I0cb6dc08530a9ba87c613fd56c81ce95cdfb7aba

Change-Id: Ib8911152f8e086c61847644e073a7055258cb75a

Change-Id: I0c76e0deaf9f4c0e6af08628e25995bacff82b16

Change-Id: I7e73ec8f46bb1530e5688709c16d9cbacc9091c1

Change-Id: I4ae98e6d63b862e52c9312f5901b4fa61f9aa6e0

Change-Id: I319ca955a8a6fe011c9b167ff9cf76895f82fb14

The axes in the top and right of the vtkChartXY charts were not behaving
correctly, the variables calculating the new transforms needed to be
initialized as in the bottom and left cases before transforming them.

Change-Id: I505f5fb198e494bf678ffc9031596b47c49d9421

The header states "shouldn't be exposed to users anymore", and so we
should probably look at how we might achieve the same thing with the API
that is intended to be exposed to users. This compiles and works with
Boost 1.49.

Change-Id: I2086f227c45692bd6aa224742369d70f71b5b264

In Python, the QVTKInteractor class wasn't inheriting any methods
from its superclass vtkRenderWindowInteractor and was useless as
a result.  The python wrappers were confused because the prefix
is "Q" instead of "vtk".  The main kits have a vtkKitHierarchy.txt
file that the wrappers can use to ascertain type and inheritance
without relying on prefixes, a simple solution here is to use the
hierarchy file that was generated for Rendering.

Change-Id: Idba365ea61d7153dfd63f678dd36318ba429dc93

We missed one variable required by the Python wrapping, which must be
defined to 0 if the kit is not being built.

Change-Id: Iba44f3c1af27bcd22ab97d1f9d4ec2fab7414bf5

Change-Id: I0e4f506374be6383c4843fef47ac7ed2e4b4099b

fa50ef90 Fix precision issues when using vtkMath::Pi()

Change-Id: If79e9b98cfaf965ed4c27c1f189c501be1fbafcb

bd2770cd FIX: vtkImplicitPlaneRepresentation does not print ivar LockNormalToCamera

75944632 EnSight6 Reader vectors per element

6dff01de Fix compiler warning and style issue

3784f6d0 Fix issue with context timestamp when using QVTKWidget2.

Change-Id: I715e9c3a2680c10b3fee317b9daa2188789f22cc

- silence 'assignment operator could not be generated' warning
  on vtkQtDebugLeaksModel::qObserver
- rename variables to avoid shadow variable warnings
- add comment about variable initialization in vtkDebugLeaks.cxx

Change-Id: Id6b65f2cc8f5b3453820197a2bc7320c3ee7a7c6

ccdaad8e BUG: Fix vtkImplicitPlaneRepresentation, redesign widget implementation:
dd214570 ENH: Automatic plan orientation in vtkImplicitPlaneWidget2

 - Re-implement the Automatic plan orientation
 - Arrows (right, left, top, bottom) shift origin instead of '<' and '>'
 - Don't observe the representation but the camera directly
 - BuildRepresentation only when needed (if rep is changed)
 - Expose to API the edge color
 - Fix active/inactive mode with change cursor
 - Avoid highlighting cut plane and changing the mouse pointer in lockToCamera mode.
 - Reactivate rescaling.
 - Add a test for trying: Press ctrl key to change the mode when interacting.

Change-Id: I9c8b8b2ccd04baf32b75178b59afc1fd0e148948

Add vtkImplicitPlaneRepresentation::SlaveNormalToCamera
Fix trailing whitespace

Change-Id: I1835eb6b31fa9ca7bde86782e19555f5f43af38b

Fix that enables EnSight6Reader to read vectors per element data in a
single file format. Single file format is when all the data for all
the time steps for one variable are in a single file.

Change-Id: I563c07e5fa07496c2326a3828c834d3f64076a14

674eea7b Properly fix the issue with reading scalar properties

9182f039 Add Qt widget for displaying objects tracked by vtkDebugLeaks
75ca1bd2 Add new api to vtkDebugLeaks to track vtk object lifetime

Corrected the original application of the patch which I did wrong. The
new patch from David fixes the issue.

Change-Id: Ib02c9f3c8e102039f1eb917a6e5fc8ab929a2b10

00ecfdbb ENH: Add a progress estimate to vtkImageThresholdConnectivity.

This fixes a couple of issues in which the single-precision
float value for pi was being used in computations involving
double-precision values.

Change-Id: I4a34f93a2b8093e95d744334f795e1ff2f7951a4

Change-Id: I7cb1e981b1863216a7cf654ad551462075e158e3

46e6489a ENH: Make python initialize vtkTuple after construction.

In C++, the vtkTuple class and its subclasses no longer initialize
their contents in the default constructor.  In order to maintain
backwards compatibility within VTK/Python and to make the behavior
more pythonic, the wrappers now perform the initialization.

The behavior is not completely backwards-compatibile, because the
vtkColor4ub class used to initialize to [0,0,0,255] and now it
initializes to [0,0,0,0], ditto for vtkColor4v and vtkColor4d.

Change-Id: I056992dfb47b8ea1c0927c7ecc621a3e0649932b

Change-Id: Ic5bc394e6cbe3d9ab8bedf1809af72912aa94411

3be5ef73 BUG: Fixed a couple of issues with bounds.

These were implicitly relying on zero initialization in order to
calculate box sizes for the axes etc.

Change-Id: If33a468d0f84e6b0a243a1522f623f291478b4ea

c4933daa BUG: Caught a few uninitialized vectors in charts.

The missed X initialization in vtkAxis was cauing some rengering issues.

Change-Id: Ibdc472b539162fda0afc415ce96ded40438697a2

62d538b5 BUG: Fixed python vtkTuple templated class test.
93862d03 STYLE: Document default vtkTuple constructor.
03b7e041 ENH: Remove default arguments, create empty ctor.
b50701c3 BUG: Fixed type for vtkColor4d.