COMP: Fix SlicerWizard/Utilities.py for Python 2.6

Use tuples instead of set literals for checking for a supported VCS
tool, as set literals are only supported in Python 2.7.

git-svn-id: http://svn.slicer.org/Slicer4/trunk@23219 3bd1e089-480b-0410-8dfb-8563597acbee
BUG: Update CTK project to fix windows build and dicom repair msg box issue.

$ git shortlog 1b2973d58..3aaa591 --no-merges
Alireza Mehrtash (1):
      Fixed a bug in repair message box

Jean-Christophe Fillion-Robin (1):
      Fix typo introduced by commit 8d376ed

git-svn-id: http://svn.slicer.org/Slicer4/trunk@23220 3bd1e089-480b-0410-8dfb-8563597acbee
ENH: separate scene views with a line

Request from Ron, adding in a horizontal line between
scene views.

Issue #1299



git-svn-id: http://svn.slicer.org/Slicer4/trunk@23221 3bd1e089-480b-0410-8dfb-8563597acbee
BUG: Fix crash with vtkMRMLSelectionNode and vtkSlicerUnitsLogic

Since r23192, the GetUnitNodes() can return empty nodes.
This triggered asserts in vtkSlicerUnitsLogic.
vtkSlicerUnitLogic is only interested in unit quantities and IDs.

git-svn-id: http://svn.slicer.org/Slicer4/trunk@23222 3bd1e089-480b-0410-8dfb-8563597acbee
BUG: #3694 check for valid image data before running pipeline

Since the display node is observing the image data directly it
may receive Modified events on image data that is not yet
completely constructed, in particular, during a DeepCopy, the scalar
fields may not yet have been copied when a ModifiedEvent is triggered
by one of the Set methods.

This change prevents a spurious vtkErrorMessage from being generated,
and so it allows the EMSegment test to pass.

git-svn-id: http://svn.slicer.org/Slicer4/trunk@23223 3bd1e089-480b-0410-8dfb-8563597acbee
BUG: Update qMRMLSliderWidget single step when range changes

The single step can depend on the range of the slider, update it when
needed.

Issues #3657, #3700
$ git shortlog 3aaa591..daaf705 --no-merges
Julien Finet (1):
      Virtualize ctkRangeWidget and ctkSliderWidget public API

git-svn-id: http://svn.slicer.org/Slicer4/trunk@23224 3bd1e089-480b-0410-8dfb-8563597acbee
COMP: Add VTKv6 Python path to launcher

It appears that the way VTKv6 chooses the location to which to install
its Python bindings has changed. As obtaining the Python version early
enough to override the path with the new VTKv6 mechanism appears to be
non-obvious/non-trivial, we instead punt, and add the location that is
now being used to the launcher's PYTHONPATH's.

Also, remove specification of VTK_INSTALL_PYTHON_USING_CMAKE, which no
longer exists in VTKv6.
ENH: Create a functional install target

Update Artichoke to commontk/Artichoke@b0cf6fc85d5a. Use new
ExternalProject_Install_CMake to install external projects when doing a
superbuild build of slicer, so that there is a functional install target
for the same.

This change is made synchronously with the merge of commontk/CTK#466
which no longer installs QtTesting to the build tree, and instead
installs it as part of the install target for CTK; thus,
SlicerBlockInstallQtTesting.cmake is (and indeed, must be, as there is
no longer an install path being exported) removed.

At least on Fedora, this is sufficient to produce a Slicer that can be
successfully run after building the 'install' target.