Over 10 years of community discussion and knowledge are maintained here as a read-only archive.
What is needed is a diagnostic utility that can be used to log regisrations and removals and provide a view component showing all the commands, mediators and proxies that are registered for which notifications at any given moment. The trick would be to have an 'intercepting Facade', which overrides all the registration and removal methods of the framework facade and before calling super, caches what actor and notification is being registered or removed. The view component that displays this info would need to be hooked to the data being collected in an out-of-band way that doesn't use the notification system so as not to affect it, if possible. I've been meaning to write this for a whils but haven't had time. If someone would like to be a hero and do so it'll be appreciated. Otherwise, eventually I'll get to it... -=Cliff>