[Telepathy-commits] [telepathy-qt4/master] Contact: Use full namespace on signals.

Andre Moreira Magalhaes (andrunko) andre.magalhaes at collabora.co.uk
Wed Mar 4 13:58:20 PST 2009


---
 TelepathyQt4/Client/contact.h |    6 +++---
 1 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/TelepathyQt4/Client/contact.h b/TelepathyQt4/Client/contact.h
index f38c0e5..e8aa0ec 100644
--- a/TelepathyQt4/Client/contact.h
+++ b/TelepathyQt4/Client/contact.h
@@ -95,13 +95,13 @@ Q_SIGNALS:
     void avatarTokenChanged(const QString &avatarToken);
     void simplePresenceChanged(const QString &status, uint type, const QString &presenceMessage);
 
-    void subscriptionStateChanged(PresenceState state);
-    void publishStateChanged(PresenceState state);
+    void subscriptionStateChanged(Telepathy::Client::Contact::PresenceState state);
+    void publishStateChanged(Telepathy::Client::Contact::PresenceState state);
     void blockStatusChanged(bool blocked);
 
     // TODO: consider how the Renaming interface should work and map to Contacts
     // I guess it would be something like:
-    // void renamedTo(QSharedPointer<Contact>)
+    // void renamedTo(QSharedPointer<Telepathy::Client::Contact>)
     // with that contact getting the same features requested as the current one. Or would we rather
     // want to signal that change right away with a handle?
 
-- 
1.5.6.5




More information about the telepathy-commits mailing list