Method OnClearLabels

Modules/SegmentationUI/src/QmitkMultiLabelInspector.cpp:1282–1320

}

void QmitkMultiLabelInspector::OnClearLabels(bool /*value*/)
{
  QString question = "Do you really want to clear the selected labels?";

  QMessageBox::StandardButton answerButton = QMessageBox::question(
    this, "Clear selected labels", question, QMessageBox::Yes | QMessageBox::Cancel, QMessageBox::Yes);

  if (answerButton == QMessageBox::Yes)
  {
    this->WaitCursorOn();

    auto labelValues = this->GetSelectedLabels();
    mitk::SegGroupModifyUndoRedoHelper::GroupIndexSetType containingGroups;
    for (const auto label : labelValues) containingGroups.insert(m_Segmentation->GetGroupIndexOfLabel(label));
    auto clearedLabelName = mitk::LabelSetImageHelper::CreateDisplayLabelName(m_Segmentation, m_Segmentation->GetLabel(labelValues.front()));
    mitk::SegGroupModifyUndoRedoHelper undoRedoGenerator(m_Segmentation, containingGroups, true, 0, true, false, true);

    m_Segmentation->EraseLabels(labelValues);

    std::ostringstream stream;
    stream << "Clear labels \"" << clearedLabelName << "\"";
    if (labelValues.size() > 1)
    {
      stream << "and " << labelValues.size() - 1 << "other labels";
    }
    undoRedoGenerator.RegisterUndoRedoOperationEvent(stream.str());

    this->WaitCursorOff();
    // this is needed as workaround for (T27307). It circumvents the fact that modifications
    // of data (here the segmentation) does not directly trigger the modification of the
    // owning node (see T27307). Therefore other code (like renderers or model views) that e.g.
    // listens to the datastorage for modification would not get notified.
    if (m_SegmentationNode.IsNotNull())
    {
      m_SegmentationNode->Modified();
      mitk::RenderingManager::GetInstance()->RequestUpdateAll();
    }
  }
}

void QmitkMultiLabelInspector::OnDeleteAffectedLabel()
{