COMP: Error due to imporoper linkage specification

inline functions are required to be declared and defined
in the same scope.  The inline specifier changed the linkage
signature an prevented this from compiling.

Undefined symbols for architecture x86_64:
  "vtkMRMLSliceNode::GetNumberOfThreeDViewIDs() const", referenced from:
      PyvtkMRMLSliceNode_GetNumberOfThreeDViewIDs(_object*, _object*) in vtkMRMLSliceNodePython.cxx.o
ld: symbol(s) not found for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see invocation)

git-svn-id: http://svn.slicer.org/Slicer4/trunk@23020 3bd1e089-480b-0410-8dfb-8563597acbee
STYLE: Remove end of line spaces

Spaces at the end of lines can cause noise in patch sets
when editors or git gobbles them up during other relatively
minor changes to files.

Removing end of line changes makes long term maintenance easier as
well.

When reviewing git histories or patch sets, the "--ignore-space-change"
option can be useful in filtering out changes due only to spacing.

i.e.
git diff HEAD~2 --ignore-space-change

git-svn-id: http://svn.slicer.org/Slicer4/trunk@23021 3bd1e089-480b-0410-8dfb-8563597acbee
STYLE: Githook warnings about excessive line length

pre-commit hook failure
-----------------------
  in file 'Libs/MRML/Logic/vtkImageLinearReslice.cxx' is longer than 160 characters.
  in file 'Modules/Loadable/Annotations/MRML/vtkMRMLAnnotationControlPointsNode.cxx' is longer than 160 characters.
  in file 'Modules/Loadable/Annotations/MRML/vtkMRMLAnnotationControlPointsStorageNode.cxx' is longer than 160 characters.
  in file 'Modules/Loadable/Annotations/Testing/Cxx/vtkMRMLAnnotationControlPointsNodeTest1.cxx' is longer than 160 characters.

git-svn-id: http://svn.slicer.org/Slicer4/trunk@23022 3bd1e089-480b-0410-8dfb-8563597acbee
BUG: Remove incorrect initialization

A compiler warning indicated incorrect initialization of
minimum value.

Slicer/Modules/CLI/RobustStatisticsSegmenter/SFLSRobustStatSegmentor3DLabelMap_single.h:133:
Slicer/Modules/CLI/RobustStatisticsSegmenter/SFLSRobustStatSegmentor3DLabelMap_single.txx:874:30: warning: implicit conversion
      from 'type' (aka 'unsigned int') to 'short' changes value from 4294967295 to -1 [-Wconstant-conversion]
  m_inputImageIntensityMin = std::numeric_limits<unsigned>::max(); // yes, it's twisted so easity to compute.

The numeric_limits type needed to be made consistent with the image.

git-svn-id: http://svn.slicer.org/Slicer4/trunk@23023 3bd1e089-480b-0410-8dfb-8563597acbee
ENH: Update SimpleITK 0.8.0 release

The manual download of distribute has been removed. The new
ez_setup.py file can fulfill the setuptools requirement.
SimpleITK's setup.py file can now utilize PowerShell, curl and wget to
download the required setuptools package of https.

From: Bradley Lowekamp <blowekamp@mail.nih.gov>

git-svn-id: http://svn.slicer.org/Slicer4/trunk@23024 3bd1e089-480b-0410-8dfb-8563597acbee
BUG: Test data was missing since Slicer4 (test was still pointing where data
 was in Slicer3)

See bug report:
http://na-mic.org/Mantis/view.php?id=3341

The test that was not working does the following:
It runs ResampleDTIVolume and the result of this operation does not matter.
What is interesting is that the test makes sure that extending itkTestMainExtend
ed.h to work with DTI did not break the normal behavior of that file and that it
 still works with scalar images too.
Therefore, it compares a scalar image with itself and verifies that the test
 passes successfully

From: fbudin69500 <fbudin@unc.edu>

git-svn-id: http://svn.slicer.org/Slicer4/trunk@23025 3bd1e089-480b-0410-8dfb-8563597acbee
ENH: Remove unused Texture and NCI volume rendering mappers

git-svn-id: http://svn.slicer.org/Slicer4/trunk@23026 3bd1e089-480b-0410-8dfb-8563597acbee
BUG: Editor updates Volume Rendering when a new label is added

Closes #3076

git-svn-id: http://svn.slicer.org/Slicer4/trunk@23027 3bd1e089-480b-0410-8dfb-8563597acbee
BUG: Accept qMRMLSceneModel::updateNodeItems with node with no scene

To have no scene in qMRMLSceneModel::updateNodeItems()) is a valid case.
When closing the scene, the "Close" state is popped and SceneClosedEvent
event is triggered, caught by an observer that eventually modify a
node, such modification is caught by a scene model that has not yet
received teh SceneClosed event. It asks if the scene is closing but it
is no longer (see vtkMRMLScene::EndState())

Closes #3513

git-svn-id: http://svn.slicer.org/Slicer4/trunk@23028 3bd1e089-480b-0410-8dfb-8563597acbee