Note: The DnD Display should use its own rendering manager, not the global one returned by mitk::RenderingManager::GetInstance(). The reason is that the global rendering manager is reinitialised by its InitializeViewsByBoundingObjects function whenever a new file is opened, recalculating a new bounding box based on all the globally visible nodes in the data storage. However, many MITK modules and plugins call RequestUpdate on the global rendering manager (RM), not on that of the focused renderer. This causes that if the DnD Display uses its own RM, it won't be updated by those plugins. An example is the Volume Visualization view. Therefore, until this is fixed in MITK, we need to use the global rendering manager, suppress the reinitialisation after file open by a preference, and should not use the MITK display and the DnD Display together in the same application.
niftk::MultiViewerEditorPrivate::~MultiViewerEditorPrivate |
( |
| ) |
|
bool niftk::MultiViewerEditorPrivate::AreCommandLineArgumentsProcessed |
( |
| ) |
|
|
static |
void niftk::MultiViewerEditorPrivate::DropNodes |
( |
QmitkRenderWindow * |
renderWindow, |
|
|
const std::vector< mitk::DataNode * > & |
nodes |
|
) |
| |
void niftk::MultiViewerEditorPrivate::ProcessCommandLineArguments |
( |
| ) |
|
MultiViewerVisibilityManager::Pointer niftk::MultiViewerEditorPrivate::m_MultiViewerVisibilityManager |
QScopedPointer<berry::IPartListener> niftk::MultiViewerEditorPrivate::m_PartListener |
mitk::RenderingManager::Pointer niftk::MultiViewerEditorPrivate::m_RenderingManager |
mitk::IRenderingManager* niftk::MultiViewerEditorPrivate::m_RenderingManagerInterface |
bool niftk::MultiViewerEditorPrivate::s_AreCommandLineArgumentsProcessed = false |
|
static |
The documentation for this class was generated from the following file: