Using Sec5Part2, connect @55 and @100 and then assign them to A57 and S58 by dragging to the Sequence Module. If you then drag @72 onto A57 on the display, you hit:
Traceback (most recent call last):
File "/Users/wb104/githome/analysis/src/python/ccpn/ui/gui/widgets/DropBase.py", line 89, in dropEvent
self._dropEventCallback(dataDict)
File "/Users/wb104/githome/analysis/src/python/ccpn/ui/gui/lib/GuiNotifier.py", line 198, in call
self._callback(callbackDict, self._args, *self._kwargs)
File "/Users/wb104/githome/analysis/src/python/ccpn/AnalysisAssign/modules/BackboneAssignmentModule.py", line 274, in _processDroppedNmrResidue
nmrResidue.connectPrevious(droppedNmrResidue)
File "/Users/wb104/githome/analysis/src/python/ccpn/core/NmrResidue.py", line 490, in connectPrevious
raise ValueError("Cannot connect assigned NmrResidue - assign the value instead")
ValueError: Cannot connect assigned NmrResidue - assign the value instead
Likely this counts as a feature (!).
But with the above exception, the Backbone Assignment module stopped working, so you could select an NmrChain in the pulldown list but the table no longer updated.
Problem was in function _processDroppedNmrResidue(). In there we have
self.nmrResidueTable.setUpdateSilence(True)
And the turning off of this needs to be in a try/finally block in case there is an exception thrown in the code (which is what happened in this case). Otherwise the table is never updated.