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 <[hidden email]>:
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