Closed cdelorme closed 11 years ago
Will be part of the contact-list update handler, once we manage to connect an active signal.
The contact-list-changed signal does not trigger for unknown reasons, assuming a break in the API, but unable to identify the cause or point of the break (is it python, C, the connection manager version, etc).
Tests on Debian/Fedora/Sugar all the same, assuming it is not the connection manager version as all the platforms used are the latest releases, so it must be a break in the python api or the c code.
In any event the best way to track user-stage changes is via status-changed, this logic is for detecting new and disconnected users, and is not yet functional nor capable of being made functional.
Add objects to track connected users and their state individually.