diff --git a/Plugins/org.mitk.gui.qt.volumevisualization/documentation/UserManual/QmitkVolumeVisualization.dox b/Plugins/org.mitk.gui.qt.volumevisualization/documentation/UserManual/QmitkVolumeVisualization.dox
index 49360ff183..c1c47212a6 100644
--- a/Plugins/org.mitk.gui.qt.volumevisualization/documentation/UserManual/QmitkVolumeVisualization.dox
+++ b/Plugins/org.mitk.gui.qt.volumevisualization/documentation/UserManual/QmitkVolumeVisualization.dox
@@ -1,154 +1,140 @@
/**
\page org_mitk_views_volumevisualization The Volume Visualization Plugin
\imageMacro{volume_visualization.svg,"Icon of the Volume Visualization Plugin",2.00}
\tableofcontents
\section QVV_Overview Overview
-The Volume Visualization Plugin is a basic tool for visualizing three dimensional medical images.
-MITK provides generic transfer function presets for medical CT data.
-These functions, that map the gray-value to color and opacity, can be interactively edited.
-Additionally, there are controls to quickly generate common used transfer function shapes
-like the threshold and bell curve to help identify a range of grey-values.
+The Volume Visualization Plugin is a basic tool for volume rendering of three dimensional medical images.
+MITK provides generic transfer function presets for medical CT and MRT data.
+These functions that map the gray-value to color and opacity can be interactively edited.
+Additionally, there are controls to quickly generate commonly used transfer function shapes like the threshold and bell curve to help identify a range of grey-values.
\imageMacro{QmitkVolumeVisualization_Overview.png,"",16.00}
-\section QVV_EnableVRPage Enable Volume Rendering
+\section QVV_EnableVRPage Volume Rendering
-\subsection QVV_LoadingImage Loading an image into the application
+\subsection QVV_LoadingImage Select an image and enable volume rendering
-Load an image into the application by
+\imageMacro{QmitkVolumeVisualization_Checkboxen.png,"",8.21}
-
-- dragging a file into the application window.
-
- selecting file / load from the menu.
-
+Select an image on top of the view and click on the checkbox left of 'Volumerendering'. Please be patient, while the image is prepared for rendering, which can take up to a half minute.
+\note
Volume Visualization imposes following restrictions on images:
-
-- It has to be a 3D-Image Scalar image, that means a normal CT or MRT.
-
- 3D+T are supported for rendering, but the histograms are not computed.
-
- Also be aware that volume visualization requires a huge amount of memory.
- Very large images may not work, unless you use the 64bit version.
+
- It has to be a 3D scalar image, that means e.g. a CT or MRT image.
+
- 3D+t images are supported for rendering, but the histograms are not computed.
+
- Also be aware that volume visualization requires a huge amount of memory. Very large images may not work unless you use the 64bit version.
-\subsection QVV_EnableVR Enable Volumerendering
-
-\imageMacro{QmitkVolumeVisualization_Checkboxen.png,"",8.21}
-
-Select an image in datamanager and click on the checkbox left of "Volumerendering".
-Please be patient, while the image is prepared for rendering, which can take up to a half minute.
\subsection QVV_LODGPU Dropdown menus for the rendering and blend modes
-Two dropdown menus allow selection of rendering mode (Default, RayCast, GPU) and the blend mode (Composite, Max, Min, Avg, Add).
+Two dropdown menus are located right next to the 'Volumerendering' checkbox. They allow you to select a rendering mode (Default, RayCast, GPU) and the blend mode (Composite, Max, Min, Avg, Add).
-Any Volume Rendering mode requires a lot of computing resources including processor, memory and often also graphics card.
-The Default selection usually finds the best rendering mode for the available hardware.
-Alternatively, it is possible to manually specify the selections RayCast and GPU.
-The RayCast selection is based on CPU computation and therefore typically slow, but allows to render without hardware acceleration.
-The GPU selection uses computing resources on the graphics card to accelerate volume rendering.
-It requires a powerful graphics card and OpenGL hardware support for shaders, but achieves much higher frame rates than software-rendering.
+Any rendering mode requires a lot of computing resources including processor, memory and often also graphics card.
+The 'Default' selection usually finds the best 'rendering' mode for the available hardware.
+Alternatively, it is possible to manually specify the selections 'RayCast' and 'GPU'.
+The 'RayCast' selection is based on CPU computation and therefore typically slow, but allows to render without hardware acceleration.
+The 'GPU' selection uses computing resources on the graphics card to accelerate volume rendering.
+It requires a powerful graphics card and OpenGL hardware support for shaders but achieves much higher frame rates than software-rendering.
-Blend modes define how the volume voxels intersected by the rendering rays are pooled. The composite mode specifies standard volume rendering,
-for which each voxel contributes equally with opacity and color. Other blend modes simply visualize the voxel of maximum /
-minimum intensity and average / add the intentities along the rendering ray.
+Blend modes define how the volume voxels, intersected by the rendering rays, are pooled. The 'Composite' mode specifies standard volume rendering,
+for which each voxel contributes equally with opacity and color. Other 'blend' modes simply visualize the voxel of the maximum /
+minimum intensity and average / add the intensities along the rendering ray.
\section QVV_PresetPage Applying premade presets
\subsection QVV_Preset Internal presets
-There are some internal presets given, that can be used with normal CT data (given in Houndsfield units).
-A large set of medical data has been tested with that presets, but it may not suit on some special cases.
+There are some internal presets given that can be used with normal CT data (given in Houndsfield units).
+A large set of medical data has been tested with those presets, but they may not suit some special cases.
-Click on the "Preset" tab for using internal or custom presets.
+Click on the 'Preset' tab for using internal or custom presets.
\imageMacro{QmitkVolumeVisualization_InternalPresets.png,"",8.30}
-- "CT Generic" is the default transferfunction that is first applied.
-
- "CT Black&White" does not use any colors, as it may be distracting on some data.
-
- "CT Cardiac" tries to increase detail on CTs from the heart.
-
- "CT Bone" emphasizes bones and shows other areas more transparent.
-
- "CT Bone (Gradient)" is like "CT Bone", but shows from other organs only the surface by using the gradient.
-
- "MR Generic" is the default transferfunction that we use on MRT data (which is not normalized like CT data).
-
- "CT Thorax small" tries to increase detail.
-
- "CT Thorax large" tries to increase detail.
+
- 'CT Generic' is the default transfer function that is first applied.
+
- 'CT Black&White' does not use any colors for the volume visualization as it may be distracting on some data.
+
- 'CT Cardiac' is well-suited for CT images containing the heart.
+
- 'CT Bone' emphasizes bones and shows other areas more transparent.
+
- 'CT Bone (Gradient)' is like 'CT Bone' but shows only the surface from other organs by using the gradient.
+
- 'MR Generic' is the default transfer function that can be used on MRT data (which is not normalized like CT data).
+
- 'CT Thorax small' is useful if only a proportion of the thorax is selected to emphasize details.
+
- 'CT Thorax large' is useful if a large proportion or the entire thorax is selected to emphasize details.
\subsection QVV_CustomPreset Saving and loading custom presets
-After creating or editing a transferfunction (see \ref QVV_Editing or \ref QVV_ThresholdBell),
-the custom transferfunction can be stored and later retrieved on the filesystem.
-Click "Save" (respectively "Load") button to save (load) the threshold-, color- and gradient function combined in a single .xml file.
-
-\section QVV_ThresholdBell Interactively create transferfunctions
+After creating or editing a transfer function (see \ref QVV_Editing or \ref QVV_ThresholdBell),
+the custom transfer function can be stored and later retrieved on the filesystem.
+Click 'Save' (respectively 'Load') button below the preset selection to save (load) the threshold-, color- and gradient function combined in a single .xml file.
-Beside the possibility to directly edit the transferfunctions (\ref QVV_Editing),
-a one-click generation of two commonly known shapes is given.
+\section QVV_ThresholdBell Interactively create transfer functions
-Both generators have two parameters, that can be modified by first clicking on the cross and then moving the mouse up/down and left/right.
+Besides the possibility to directly edit the transfer functions (\ref QVV_Editing), the plugin provides two commonly known shapes to quickly generate transfer functions with a few clicks. Both generators have two parameters that can be modified by first clicking on the cross and then moving the mouse up/down and left/right.
-The first parameter "center" (controlled by horizontal movement of the mouse) specifies the gravalue where the center of the shape will be located.
+The first parameter 'center' (controlled by horizontal movement of the mouse) specifies the gray value where the center of the shape will be located.
-The second parameter "width" (controlled by vertical movement of the mouse) specifies the width (or steepness) of the shape.
+The second parameter 'width' (controlled by vertical movement of the mouse) specifies the width (or steepness) of the shape.
\subsection Threshold
-Click on the "Threshold" tab to active the threshold function generator.
+Click on the 'Threshold' tab to activate the threshold function generator.
\imageMacro{QmitkVolumeVisualization_Threshold.png,"",8.21}
-A threshold shape begins with zero and raises to one across the "center" parameter. Lower widths results in steeper threshold functions.
+A threshold shape begins with zero and raises to one across the 'center' parameter. Lower widths result in steeper threshold functions.
\subsection Bell
-Click on the "Bell" tab to active the threshold function generator.
+Click on the 'Bell' tab to activate the bell-shaped threshold function generator.
\imageMacro{QmitkVolumeVisualization_Bell.png,"",8.23}
-A threshold shape begins with zero and raises to one at the "center" parameter and the lowers agains to zero. The "width" parameter correspondens to the width of the bell.
+A threshold shape begins with zero and raises to one at the 'center' parameter and then lowers again to zero. The 'width' parameter corresponds to the width of the bell.
-\section QVV_Editing Customize transferfunctions in detail
+\section QVV_Editing Customize transfer functions in detail
-\subsection QVV_Navigate Choosing grayvalue interval to edit
+\subsection QVV_Navigate Choosing gray value interval to edit
\imageMacro{QmitkVolumeVisualization_Slider.png,"",8.23}
-To navigate across the grayvalue range or to zoom in some ranges use the "range"-slider.
+To navigate across the gray value range or to zoom in some ranges use the 'range'-slider.
All three function editors have in common following:
- By left-clicking a new point is added.
- By right-clicking a point is deleted.
- By left-clicking and holding, an exisiting point can be dragged.
- By pressing arrow keys, the currently selected point is moved.
-
- By pressing the "DELETE" key, the currently selected point is deleted.
+
- By pressing the 'DELETE' key, the currently selected point is deleted.
- Between points the transferfunctions are linear interpolated.
-There are three transferfunctions to customize:
+There are three transfer functions to customize:
\subsection QVV_GO Grayvalue -> Opacity
-\imageMacro{QmitkVolumeVisualization_Opacity.png,"grayvalues will be mapped to opacity.",8.04}
+\imageMacro{QmitkVolumeVisualization_Opacity.png,"Gray values will be mapped to opacity.",8.04}
+
+An opacity of 0 means total transparent, an opacity of 1 means total opaque. The opacity editor allows changing the opacity for all gray values independently. You can alter the position of control points using your mouse. You can add control points by left-clicking on the graph. To remove a control point again you can right-click on the respective point.
-An opacity of 0 means total transparent, an opacity of 1 means total opaque.
\subsection QVV_GC Grayvalue -> Color
-\imageMacro{QmitkVolumeVisualization_Color.png,"grayvalues will be mapped to color.",8.81}
+\imageMacro{QmitkVolumeVisualization_Color.png,"Gray values will be mapped to color.",8.81}
-The color transferfunction editor also allows by double-clicking a point to change its color.
+The color transfer function editor also allows you to change its color by double-clicking a point. You can add color control points by left-clicking on the color bar. To remove a control point again right-click on the respective point.
\subsection QVV_GGO Grayvalue and Gradient -> Opacity
\imageMacro{QmitkVolumeVisualization_Gradient.png,"",8.85}
-Here the influence of the gradient is controllable at specific grayvalues.
-
+The gradient editor allows you to change the gradient influence for all gray values independently. You can move the existing control points using your mouse. Additionally, you can add control points by left-clicking on the graph. To remove a control point again, right-click on the respective point.
*/
diff --git a/Plugins/org.mitk.gui.qt.volumevisualization/documentation/UserManual/QmitkVolumeVisualization_Bell.png b/Plugins/org.mitk.gui.qt.volumevisualization/documentation/UserManual/QmitkVolumeVisualization_Bell.png
index 7cf0b2eed9..a4df90bd88 100644
Binary files a/Plugins/org.mitk.gui.qt.volumevisualization/documentation/UserManual/QmitkVolumeVisualization_Bell.png and b/Plugins/org.mitk.gui.qt.volumevisualization/documentation/UserManual/QmitkVolumeVisualization_Bell.png differ
diff --git a/Plugins/org.mitk.gui.qt.volumevisualization/documentation/UserManual/QmitkVolumeVisualization_Checkboxen.png b/Plugins/org.mitk.gui.qt.volumevisualization/documentation/UserManual/QmitkVolumeVisualization_Checkboxen.png
index f395d4cb7d..dac50d7795 100644
Binary files a/Plugins/org.mitk.gui.qt.volumevisualization/documentation/UserManual/QmitkVolumeVisualization_Checkboxen.png and b/Plugins/org.mitk.gui.qt.volumevisualization/documentation/UserManual/QmitkVolumeVisualization_Checkboxen.png differ
diff --git a/Plugins/org.mitk.gui.qt.volumevisualization/documentation/UserManual/QmitkVolumeVisualization_Color.png b/Plugins/org.mitk.gui.qt.volumevisualization/documentation/UserManual/QmitkVolumeVisualization_Color.png
index befafba215..4b346432fe 100644
Binary files a/Plugins/org.mitk.gui.qt.volumevisualization/documentation/UserManual/QmitkVolumeVisualization_Color.png and b/Plugins/org.mitk.gui.qt.volumevisualization/documentation/UserManual/QmitkVolumeVisualization_Color.png differ
diff --git a/Plugins/org.mitk.gui.qt.volumevisualization/documentation/UserManual/QmitkVolumeVisualization_Gradient.png b/Plugins/org.mitk.gui.qt.volumevisualization/documentation/UserManual/QmitkVolumeVisualization_Gradient.png
index c9bf5ef70f..d4ba5b74f9 100644
Binary files a/Plugins/org.mitk.gui.qt.volumevisualization/documentation/UserManual/QmitkVolumeVisualization_Gradient.png and b/Plugins/org.mitk.gui.qt.volumevisualization/documentation/UserManual/QmitkVolumeVisualization_Gradient.png differ
diff --git a/Plugins/org.mitk.gui.qt.volumevisualization/documentation/UserManual/QmitkVolumeVisualization_InternalPresets.png b/Plugins/org.mitk.gui.qt.volumevisualization/documentation/UserManual/QmitkVolumeVisualization_InternalPresets.png
index a769755e2a..78bd1e14c1 100644
Binary files a/Plugins/org.mitk.gui.qt.volumevisualization/documentation/UserManual/QmitkVolumeVisualization_InternalPresets.png and b/Plugins/org.mitk.gui.qt.volumevisualization/documentation/UserManual/QmitkVolumeVisualization_InternalPresets.png differ
diff --git a/Plugins/org.mitk.gui.qt.volumevisualization/documentation/UserManual/QmitkVolumeVisualization_Opacity.png b/Plugins/org.mitk.gui.qt.volumevisualization/documentation/UserManual/QmitkVolumeVisualization_Opacity.png
index c31fbc8aca..79f549f869 100644
Binary files a/Plugins/org.mitk.gui.qt.volumevisualization/documentation/UserManual/QmitkVolumeVisualization_Opacity.png and b/Plugins/org.mitk.gui.qt.volumevisualization/documentation/UserManual/QmitkVolumeVisualization_Opacity.png differ
diff --git a/Plugins/org.mitk.gui.qt.volumevisualization/documentation/UserManual/QmitkVolumeVisualization_Overview.png b/Plugins/org.mitk.gui.qt.volumevisualization/documentation/UserManual/QmitkVolumeVisualization_Overview.png
index 2c190a8ce2..555de51a10 100644
Binary files a/Plugins/org.mitk.gui.qt.volumevisualization/documentation/UserManual/QmitkVolumeVisualization_Overview.png and b/Plugins/org.mitk.gui.qt.volumevisualization/documentation/UserManual/QmitkVolumeVisualization_Overview.png differ
diff --git a/Plugins/org.mitk.gui.qt.volumevisualization/documentation/UserManual/QmitkVolumeVisualization_Slider.png b/Plugins/org.mitk.gui.qt.volumevisualization/documentation/UserManual/QmitkVolumeVisualization_Slider.png
index f65e9d6da5..c1237a7f12 100644
Binary files a/Plugins/org.mitk.gui.qt.volumevisualization/documentation/UserManual/QmitkVolumeVisualization_Slider.png and b/Plugins/org.mitk.gui.qt.volumevisualization/documentation/UserManual/QmitkVolumeVisualization_Slider.png differ
diff --git a/Plugins/org.mitk.gui.qt.volumevisualization/documentation/UserManual/QmitkVolumeVisualization_Threshold.png b/Plugins/org.mitk.gui.qt.volumevisualization/documentation/UserManual/QmitkVolumeVisualization_Threshold.png
index fe6fc3b653..a12fcf586f 100644
Binary files a/Plugins/org.mitk.gui.qt.volumevisualization/documentation/UserManual/QmitkVolumeVisualization_Threshold.png and b/Plugins/org.mitk.gui.qt.volumevisualization/documentation/UserManual/QmitkVolumeVisualization_Threshold.png differ
diff --git a/Plugins/org.mitk.gui.qt.volumevisualization/src/internal/QmitkVolumeVisualizationView.cpp b/Plugins/org.mitk.gui.qt.volumevisualization/src/internal/QmitkVolumeVisualizationView.cpp
index 51d291a500..7ab3ab1e54 100755
--- a/Plugins/org.mitk.gui.qt.volumevisualization/src/internal/QmitkVolumeVisualizationView.cpp
+++ b/Plugins/org.mitk.gui.qt.volumevisualization/src/internal/QmitkVolumeVisualizationView.cpp
@@ -1,291 +1,292 @@
/*============================================================================
The Medical Imaging Interaction Toolkit (MITK)
Copyright (c) German Cancer Research Center (DKFZ)
All rights reserved.
Use of this source code is governed by a 3-clause BSD license that can be
found in the LICENSE file.
============================================================================*/
#include "QmitkVolumeVisualizationView.h"
#include
#include
#include
#include
#include
#include
#include
#include
#include
#include
#include
#include
const std::string QmitkVolumeVisualizationView::VIEW_ID = "org.mitk.views.volumevisualization";
enum
{
DEFAULT_RENDERMODE = 0,
RAYCAST_RENDERMODE = 1,
GPU_RENDERMODE = 2
};
QmitkVolumeVisualizationView::QmitkVolumeVisualizationView()
: QmitkAbstractView()
, m_Controls(nullptr)
{
}
void QmitkVolumeVisualizationView::SetFocus()
{
}
void QmitkVolumeVisualizationView::CreateQtPartControl(QWidget* parent)
{
m_Controls = new Ui::QmitkVolumeVisualizationViewControls;
m_Controls->setupUi(parent);
m_Controls->volumeSelectionWidget->SetDataStorage(GetDataStorage());
m_Controls->volumeSelectionWidget->SetNodePredicate(mitk::NodePredicateAnd::New(
mitk::TNodePredicateDataType::New(),
mitk::NodePredicateOr::New(mitk::NodePredicateDimension::New(3), mitk::NodePredicateDimension::New(4)),
mitk::NodePredicateNot::New(mitk::NodePredicateProperty::New("helper object"))));
-
m_Controls->volumeSelectionWidget->SetSelectionIsOptional(true);
m_Controls->volumeSelectionWidget->SetEmptyInfo(QString("Please select a 3D / 4D image volume"));
m_Controls->volumeSelectionWidget->SetPopUpTitel(QString("Select image volume"));
// Fill the transfer function presets in the generator widget
std::vector names;
mitk::TransferFunctionInitializer::GetPresetNames(names);
for (const auto& name : names)
{
m_Controls->transferFunctionGeneratorWidget->AddPreset(QString::fromStdString(name));
}
// see enum in vtkSmartVolumeMapper
m_Controls->renderMode->addItem("Default");
m_Controls->renderMode->addItem("RayCast");
m_Controls->renderMode->addItem("GPU");
// see vtkVolumeMapper::BlendModes
m_Controls->blendMode->addItem("Comp");
m_Controls->blendMode->addItem("Max");
m_Controls->blendMode->addItem("Min");
m_Controls->blendMode->addItem("Avg");
m_Controls->blendMode->addItem("Add");
connect(m_Controls->volumeSelectionWidget, &QmitkSingleNodeSelectionWidget::CurrentSelectionChanged,
this, &QmitkVolumeVisualizationView::OnCurrentSelectionChanged);
connect(m_Controls->enableRenderingCB, SIGNAL(toggled(bool)), this, SLOT(OnEnableRendering(bool)));
connect(m_Controls->renderMode, SIGNAL(activated(int)), this, SLOT(OnRenderMode(int)));
connect(m_Controls->blendMode, SIGNAL(activated(int)), this, SLOT(OnBlendMode(int)));
connect(m_Controls->transferFunctionGeneratorWidget, SIGNAL(SignalUpdateCanvas()),
m_Controls->transferFunctionWidget, SLOT(OnUpdateCanvas()));
connect(m_Controls->transferFunctionGeneratorWidget, SIGNAL(SignalTransferFunctionModeChanged(int)),
SLOT(OnMitkInternalPreset(int)));
m_Controls->enableRenderingCB->setEnabled(false);
m_Controls->blendMode->setEnabled(false);
m_Controls->renderMode->setEnabled(false);
m_Controls->transferFunctionWidget->setEnabled(false);
m_Controls->transferFunctionGeneratorWidget->setEnabled(false);
+
+ m_Controls->volumeSelectionWidget->SetAutoSelectNewNodes(true);
}
void QmitkVolumeVisualizationView::OnMitkInternalPreset(int mode)
{
if (m_SelectedNode.IsExpired())
{
return;
}
auto node = m_SelectedNode.Lock();
mitk::TransferFunctionProperty::Pointer transferFuncProp;
if (node->GetProperty(transferFuncProp, "TransferFunction"))
{
// first item is only information
if (--mode == -1)
return;
// -- Creat new TransferFunction
mitk::TransferFunctionInitializer::Pointer tfInit = mitk::TransferFunctionInitializer::New(transferFuncProp->GetValue());
tfInit->SetTransferFunctionMode(mode);
RequestRenderWindowUpdate();
m_Controls->transferFunctionWidget->OnUpdateCanvas();
}
}
void QmitkVolumeVisualizationView::OnCurrentSelectionChanged(QList nodes)
{
m_SelectedNode = nullptr;
if (nodes.empty() || nodes.front().IsNull())
{
UpdateInterface();
return;
}
auto selectedNode = nodes.front();
auto image = dynamic_cast(selectedNode->GetData());
if (nullptr != image)
{
m_SelectedNode = selectedNode;
}
UpdateInterface();
}
void QmitkVolumeVisualizationView::OnEnableRendering(bool state)
{
if (m_SelectedNode.IsExpired())
{
return;
}
m_SelectedNode.Lock()->SetProperty("volumerendering", mitk::BoolProperty::New(state));
UpdateInterface();
RequestRenderWindowUpdate();
}
void QmitkVolumeVisualizationView::OnRenderMode(int mode)
{
if (m_SelectedNode.IsExpired())
{
return;
}
auto selectedNode = m_SelectedNode.Lock();
bool usegpu = false;
bool useray = false;
if (DEFAULT_RENDERMODE == mode)
{
useray = true;
usegpu = true;
}
else if (GPU_RENDERMODE == mode)
{
usegpu = true;
}
else if (RAYCAST_RENDERMODE == mode)
{
useray = true;
}
selectedNode->SetProperty("volumerendering.usegpu", mitk::BoolProperty::New(usegpu));
selectedNode->SetProperty("volumerendering.useray", mitk::BoolProperty::New(useray));
RequestRenderWindowUpdate();
}
void QmitkVolumeVisualizationView::OnBlendMode(int mode)
{
if (m_SelectedNode.IsExpired())
{
return;
}
auto selectedNode = m_SelectedNode.Lock();
bool usemip = false;
if (vtkVolumeMapper::MAXIMUM_INTENSITY_BLEND == mode)
{
usemip = true;
}
selectedNode->SetProperty("volumerendering.usemip", mitk::BoolProperty::New(usemip));
selectedNode->SetProperty("volumerendering.blendmode", mitk::IntProperty::New(mode));
RequestRenderWindowUpdate();
}
void QmitkVolumeVisualizationView::UpdateInterface()
{
if (m_SelectedNode.IsExpired())
{
// turnoff all
m_Controls->enableRenderingCB->setChecked(false);
m_Controls->enableRenderingCB->setEnabled(false);
m_Controls->blendMode->setCurrentIndex(0);
m_Controls->blendMode->setEnabled(false);
m_Controls->renderMode->setCurrentIndex(0);
m_Controls->renderMode->setEnabled(false);
m_Controls->transferFunctionWidget->SetDataNode(nullptr);
m_Controls->transferFunctionWidget->setEnabled(false);
m_Controls->transferFunctionGeneratorWidget->SetDataNode(nullptr);
m_Controls->transferFunctionGeneratorWidget->setEnabled(false);
return;
}
bool enabled = false;
auto selectedNode = m_SelectedNode.Lock();
selectedNode->GetBoolProperty("volumerendering", enabled);
m_Controls->enableRenderingCB->setEnabled(true);
m_Controls->enableRenderingCB->setChecked(enabled);
if (!enabled)
{
// turnoff all except volumerendering checkbox
m_Controls->blendMode->setCurrentIndex(0);
m_Controls->blendMode->setEnabled(false);
m_Controls->renderMode->setCurrentIndex(0);
m_Controls->renderMode->setEnabled(false);
m_Controls->transferFunctionWidget->SetDataNode(nullptr);
m_Controls->transferFunctionWidget->setEnabled(false);
m_Controls->transferFunctionGeneratorWidget->SetDataNode(nullptr);
m_Controls->transferFunctionGeneratorWidget->setEnabled(false);
return;
}
// otherwise we can activate em all
m_Controls->blendMode->setEnabled(true);
m_Controls->renderMode->setEnabled(true);
// Determine Combo Box mode
{
bool usegpu = false;
bool useray = false;
bool usemip = false;
selectedNode->GetBoolProperty("volumerendering.usegpu", usegpu);
selectedNode->GetBoolProperty("volumerendering.useray", useray);
selectedNode->GetBoolProperty("volumerendering.usemip", usemip);
int blendMode;
if (selectedNode->GetIntProperty("volumerendering.blendmode", blendMode))
m_Controls->blendMode->setCurrentIndex(blendMode);
if (usemip)
m_Controls->blendMode->setCurrentIndex(vtkVolumeMapper::MAXIMUM_INTENSITY_BLEND);
int mode = DEFAULT_RENDERMODE;
if (useray)
mode = RAYCAST_RENDERMODE;
else if (usegpu)
mode = GPU_RENDERMODE;
m_Controls->renderMode->setCurrentIndex(mode);
}
m_Controls->transferFunctionWidget->SetDataNode(selectedNode);
m_Controls->transferFunctionWidget->setEnabled(true);
m_Controls->transferFunctionGeneratorWidget->SetDataNode(selectedNode);
m_Controls->transferFunctionGeneratorWidget->setEnabled(true);
}