object-manager: implement the 'installed' signal and improve state management
The 'installed' signal can be used to know that there are no known objects that are being prepared internally, so the object manager is ready to use. This also improves internal state management so that the 'objects-changed' signal cannot be fired earlier than it should. Previously there were corner cases with complex proxy features, as the object manager relied on the fact that after a core 'sync' it is safe to assume that all proxies are augmented... that's not always the case.
Please register or sign in to comment