Method OnDeleteLabels

Modules/SegmentationUI/src/QmitkMultiLabelInspector.cpp:1361–1401

}

void QmitkMultiLabelInspector::OnDeleteLabels(bool /*value*/)
{
  QString question = "Do you really want to remove the selected labels?";
  QMessageBox::StandardButton answerButton = QMessageBox::question(
    this, "Remove selected labels", question, QMessageBox::Yes | QMessageBox::Cancel, QMessageBox::Yes);

  if (answerButton == QMessageBox::Yes)
  {
    auto labelValues = this->GetSelectedLabels();

    if (labelValues.empty()) return;

    this->WaitCursorOn();

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

    m_Segmentation->RemoveLabels(this->GetSelectedLabels());

    std::ostringstream stream;
    stream << "Remove labels \"" << deletedLabelName << "\"";
    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();
    }
  }
}

void QmitkMultiLabelInspector::OnMergeLabels(bool /*value*/)
{