This fixes bug 12772, where an API change in Boost was causing
compilation failures using Boost 1.38. Thanks to Orion Poplawski for
reporting the issue and posting the patch.

Change-Id: I491b0f1650c0be19319533306eb10597dc96fa06

A hack in QWidgetPrivate::repaint_sys (qbackingstore.cpp) checks the type
of the widget QPaintEngine. If it is an OpenGL engine, it then forces the
 repaint to be done on the entire widget instead of the dirty region.

Changing the paint engine type, ensures QVTKWidget to be fully repainted on Windows when resizing the widget.
This fix makes the behavior of QVTKWidget similar to QVTKWidget2.
It has visible results when the flag Qt::WA_PaintOnScreen is set on Windows (not the case because of the previous commit)

Change-Id: I5ce944d73c5931ca9423b9cc848bc1ede6bf5b91

Change-Id: Ib578f85219ffe1c5b138fab99598326f327cac51

Change-Id: I3cb159609d3274d15b420a8fab1a6dc9f269372e

The platform check for linux was specifically looking for a three part
version string (ex: Linux-MAJOR.MINOR.PATCH, Linux-2.6.36, etc.).  This
will fail when using the newly released 3.0 kernel as it is only a 2-part
version string (Linux-3.0).  The version check has been modified to only

Change-Id: Ide69541d8baa4001daa0b3d5de990291117f244a

Change-Id: I4275821d50dba3cc0d6ec50ed0e1cc682c23ccc9

Contol the number of ruler subdivisions;
provide access to some of the properties;
controls for managing the size of labels.

Updated TestDistanceWidget and enabled and updated
TestDistanceWidget3D to test new methods.
Fixed compilation warning in updated
TestDistanceWidget3D.
Updated baseline images pushed to github at:
https://github.com/naucoin/VTKData/commit/7f7b5d572af79d33c53a00b99180c0f6d365f4be

Change-Id: I20856c964122fea03541bbc626ab8c51c1d65ded

This adds customized functions for traverising the input scalars in
one pass to compute the min-max-gradient_max space leaping structure.
Caching of the output to ensure that the entire output is not regenerated
based on flags is also added. It was missing earlier.

Please see the earlier two feature commits :

  MultiThread-SpaceLeaping-VolumeReadering-Feature*

Having a 1D texture results in having xsize == 1 or ysize == 1.
It would be a division by 0.
Add test to try different texture sizes and see if it crashes.

Change-Id: I10142c62a9448563b6e217be3441ecf3466149db

They both use sqlite://local.db and can corrupt each others test results.

Change-Id: Ie27e0026c929944d005364a0cc64e0647b737f4a

Cast the double to int.

This reverts commit 06385b75.

Change-Id: If121392e3b57759f923a6daaf13a189be83f0aeb

Should just be rewritten to not use fixed size arrays >_<.

Change-Id: I18cddbfa9e1c4f9b8d1acf40a7e92a694e9bf9cd

Fixes VTK bug #0012385

Change-Id: I36da4a37b75d038cc74fb2931aff3e0350bdac51