"as yet unclassified" protocol remains when empty
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
Hi Ben, I think it has already been noticed as a bug, so it will be corrected. Not sure there is already an issue about it, however. Regards, Thierry Le 01/10/2013 15:43, btc@openinworld.com a écrit :
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
-- Thierry Goubier CEA list Laboratoire des Fondations des Systèmes Temps Réel Embarqués 91191 Gif sur Yvette Cedex France Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95
Thanks Thierry. Searching didn't turn up anything, so I logged it https://pharo.fogbugz.com/f/cases/11772/as-yet-unclassified-protocol-remains... Goubier Thierry wrote:
Hi Ben,
I think it has already been noticed as a bug, so it will be corrected. Not sure there is already an issue about it, however.
Regards,
Thierry
Le 01/10/2013 15:43, btc@openinworld.com a écrit :
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
participants (2)
-
btc@openinworld.com -
Goubier Thierry