Hi Karl,

update your image and evaluate "ReleaseBuilder discardUserObjects". Then see whether those uniclasses appear in the code browser again. Should work now.

Best,
Marcel
Am 27.05.2018 13:28:31 schrieb Marcel Taeumel <marcel.taeumel at hpi.de>:
Hi, there.

The main issue is that uni-classes are in several environments at the moment. See:
Player class >> #environment

:-(

On deletion, they will not get removed from the default/global environment. That confuses the system code browser. This might be the actual bug: Why are uni-classes stored in the default environment?

Best,
Marcel
Am 27.05.2018 13:02:50 schrieb karl ramberg <karlramberg at gmail.com>:
Hi,
I ran across this bug trying to clean up spurious loaded Player classes.

Removing a class in UserObjects in the Browser using menu option 'remove class(X)'.
PlayerXX classes  are replaced by AnObsoletePlayerXX instead in the list.

If you click on the AnObsoletePlayerXX you get a DNU from the browser.

Best,
Karl
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.squeakfoundation.org/pipermail/squeak-dev/attachments/20180528/2ce513f8/attachment.html>