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

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

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.

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

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.

The vtkTuple derived classes do not initialize members unless a
constructor with an initialization argument is called. Corrected the
tests to call such a constructor.

Change-Id: I723db01184859969cbf1f7b0da62248b4633ec12

Change-Id: If655975d89c063efa3c1ed35e60c6edac3ed38aa

This change is in line with the changes made to the other vtkTuple
derived classes, without using typedefs these changes must be fed
through to each named type.

Change-Id: Ife7005aff2191c49f6c0d08cf3159920edc2f696

Thanks to David Gobbi for pointing out the error.

Change-Id: If2db78df87eeee3af894dc986dc5c7fb63e1262b

864acded BUG: Fix memory leak in vtkMassProperties in error checking return

fa84d113 COMP: Enclose legacy implementation in ifdef block.

Use a smart pointer on ptIds to avoid the need to delete through all
possible return paths.

Change-Id: I19000b87f1e9fdf80993043b26cdb6e0946a2aeb

Forgot to include the GetActiveAnnotationLink implementation in the
ifdef block, causing compilation errors when legacy remove is on.

Change-Id: I8bc4646c689da1b070d69c7634204c3f65ff3cfd

a633baca ENH: Removed duplication on GetPlaneFromBond.
6787055a ENH: Fix leaks on failure, made test fall through.
9306a4d9 ENH: Simplification of the chemistry core API.
ad5b329b ENH: Simplify the vtkAtom API.

Change-Id: I3aed58d875bd7080d8e369769b476f59447fa5e5

Change-Id: I5c45fbc337fc7c1fccdbef4c831624862f7cbfb9

e8da0da8 COMP: QVTK uses X API but doesn't link to X libs.

ce7fee0e ENH: Use GetAnnotationLink() for consistency.

ef1f6028 BUG: Converted QImage return object was ignored.

Also added a little extra const safety to the atom and bond classes.

Change-Id: I46f529b0c185da65b92523dcd54ff6e26cf52538

It is much more useful to see all error output from a test, rather than
failure on the first issue. I also removed several unused headers.

Change-Id: I58077869b9c8e45f8172bebda0e3babcff9c5bd8

Change-Id: I95290687af241a37d8734c2ae16d9b4a1cc00ff3

65a75078 ENH: Added scalar multipliers for vectors.
88aa2feb ENH: Remove implicit zero construction from colors.
586692d6 BUG: Get rid of implicit zero construction.

24fef873 COMP: Remove illegal "degree" char from literal.

Non-unicode string literals must be ascii in VTK.

Change-Id: Id8d9cbc96fa1d124fdf00b82f8b638b388a58891

The Clang 3.0 compiler is unable to link QVTK due to X symbols it cannot
find. The QVTKWidget::x11_setup_window() function makes calls to X, and
so if VTK_USE_X is defined we should be linking.

Change-Id: I9a8a4f18dd6c1b86892c078dd5e0054a79177866