Looking at the data manager we find
node->SetSelected(..) in void QmitkDataManagerView::NodeSelectionChanged(const QItemSelection& /*selected*/, const QItemSelection& /*deselected*/).
This sets the selected property of the data node so that other plugins can easily find out if a node has been selected. This is currently used in T25483.
Since we use the new selection concept - also with a focus on a more local selection - we do not maintain the selected property anymore (apart from the data manager).
We should investigate if this property is still needed / used by other plugins and if so how we want to maintain the selected property using the new selection concept.
For usage inside the LevelWindowManager see branch in this task.
Next steps
- look through the mentioned classes and find out how the "selected" property is used
- think about the new selection concept: does the use of the "selected" property make sense with the new local selection concept (nodes can be selected in a plugin instead of the data manager / nodes can be selected in a plugin that has nothing to do with one of the above mentioned classes)
- see if the mentioned classes are able to be connected with the selection bus (only available inside plugins - blueberry dependent) - as an example see level window manager inside this task (mitk::LevelWindowManager::ServiceSelectionChanged).
- alternatively think about the consequences if each local selection (widget) of a plugin view sets the "selected" property of a locally selected node - what implications does this have on the above mentioned classes?