BUG: Add sanity checks to MRMLCommandLineModule node to prevent crash using python

* Method "IsValidParamId" and "IsValidGroupId" have been added

* Const qualifier has been added to existing methods

See http://na-mic.org/Mantis/view.php?id=2600

Fixes #2600

git-svn-id: http://svn.slicer.org/Slicer4/trunk@21100 3bd1e089-480b-0410-8dfb-8563597acbee
ENH: Simplify vtkMRMLCommandLineModuleNode API

* SetParameterAs* methods now return a boolean to indicate if the call was
successful

* Now python wrapping support std::string, remove duplicated methods

git-svn-id: http://svn.slicer.org/Slicer4/trunk@21101 3bd1e089-480b-0410-8dfb-8563597acbee
ENH: Add support for display node Views in Model Displayable Manager

Note that there is currently no GUI to specify the view nodes for a
vtkMRMLModelDisplayNode.

git-svn-id: http://svn.slicer.org/Slicer4/trunk@21102 3bd1e089-480b-0410-8dfb-8563597acbee
ENH: Add qMRMLVolumeWidget, an abstract vtkMRMLScalarVolumeNode widget

qMRMLWindowLevelWidget is factorized with qMRMLVolumeThresholdWidget.
qMRMLVolumeThresholdWidget deriving from qMRMLVolumeWidget, the
range popup widget is added (the same than qMRMLWindowLevelWidget).

This work should be extended in issue #1694

Closes #2601

git-svn-id: http://svn.slicer.org/Slicer4/trunk@21103 3bd1e089-480b-0410-8dfb-8563597acbee
BUG: Update baseline for Camera displayable manager

Following redesign/fix in r21081, the baseline image must be updated.

git-svn-id: http://svn.slicer.org/Slicer4/trunk@21104 3bd1e089-480b-0410-8dfb-8563597acbee
COMP: Fix unused variable warnings

git-svn-id: http://svn.slicer.org/Slicer4/trunk@21105 3bd1e089-480b-0410-8dfb-8563597acbee
COMP: Fix unused variable warnings in qMRMLVolumeWidget

git-svn-id: http://svn.slicer.org/Slicer4/trunk@21106 3bd1e089-480b-0410-8dfb-8563597acbee
BUG: Return appropriate IDs in vtkMRMLPETProceduralColorNode::GetTypeAsIDString()

From Julien: While this will fix the problem, it doesn't fix the root
cause of the issue.
a) there is a duplication of information between "IDs" and "type strings"
b) I don't think a MRML node should know about how IDs are set.
It doesn't even set the SingletonTag to itself, however
vtkMRMLColorLogic is the one that sets the ID (by setting the singleton),
so vtkMRMLColorLogic should be the one that know about IDs. Actually,
to be really consistent, only the scene knows about IDs
(vtkMRMLScene::GenerateUniqueID).


See http://www.na-mic.org/Bug/view.php?id=2613

Fixes #2613

git-svn-id: http://svn.slicer.org/Slicer4/trunk@21107 3bd1e089-480b-0410-8dfb-8563597acbee
STYLE: change debugging print out to a debug macro

git-svn-id: http://svn.slicer.org/Slicer4/trunk@21108 3bd1e089-480b-0410-8dfb-8563597acbee
BUG: volume rendering initialization procedure has been updated so that no extra ROIs should be created when switching between steps; fixes #2598
BUG: popup error message display added when registration failed, addresses #2587; the root of the issue is #1635, which remains unresolved, but causes problems only on some Linux configurations


git-svn-id: http://svn.slicer.org/Slicer4/trunk@21109 3bd1e089-480b-0410-8dfb-8563597acbee
STYLE: don't print out loading module debugging statement during testing as it can cause dashboard output to be truncated before the extension test output is shown

git-svn-id: http://svn.slicer.org/Slicer4/trunk@21110 3bd1e089-480b-0410-8dfb-8563597acbee
STYLE: Remove vtkMRMLXXXColorYYYNode::GetTypeAsIDString()

a) there was a duplication of information between "IDs" and "GetTypeAsString"
b) A color node should not know about how IDs are set.
It doesn't even set the SingletonTag to itself,
however vtkMRMLColorLogic is the one that sets the ID
(by setting the singleton), so vtkMRMLColorLogic should be the one
that knows about IDs.
Actually, to be really consistent, only the scene knows about IDs
(see vtkMRMLScene::GenerateUniqueID).

Closes #2613

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