I wanted to check this was not a feature before reporting an issue.Previously in Pharo 2.0, when the protocol "as yet unclassified" became empty, it disappeared.
In Pharo 30434, it does not disappear when empty. Really a small thing, but I prefer the previous behaviour.
cheers -ben
