We recently updated some important plugins to work with the new selection concept and new selection widgets (see T24775: Refactor plugins to use the new node selection widgets).
Then we had a discussion about the default selection mode of the selection widgets (see T27498: [Selection widgets] Define default for auto selection / listening mechanism).

We are now facing an non intuitive situation where a developer of a plugin has to know that calling SelectionWidget->SetAutoSelectNewNodes(true); needs to happen after something like connect(SelectionWidget, &QmitkSingleNodeSelectionWidget::CurrentSelectionChanged, this, &SomePlugin::OnCurrentSelectionChanged); (which is sometimes put into a function called CreateConnections or SetupConnections).

The reason for that is that SetAutoSelectNewNodes creates a new selection and eventually emits the signal CurrentSelectionChanged, which has not been connected, if the call happens before the connect.

I want to discuss this and talk about possible solutions or our default way to do this. We now have some views that simply put the call to SetAutoSelectNewNodes at the end of (typically) CreateQtPartControl. This is absolutely valid but I'm not sure if this is the best option.