[Telepathy-commits] [telepathy-qt4/master] DBusProxy: format enum documentation the way doxygen wants it
Simon McVittie
simon.mcvittie at collabora.co.uk
Tue Feb 24 03:09:49 PST 2009
---
TelepathyQt4/Client/dbus-proxy.cpp | 16 ++++++++++------
1 files changed, 10 insertions(+), 6 deletions(-)
diff --git a/TelepathyQt4/Client/dbus-proxy.cpp b/TelepathyQt4/Client/dbus-proxy.cpp
index 27ac341..c54b801 100644
--- a/TelepathyQt4/Client/dbus-proxy.cpp
+++ b/TelepathyQt4/Client/dbus-proxy.cpp
@@ -59,14 +59,18 @@ namespace Client
* Specifies if the interface being supported by the remote object should be
* checked by optionalInterface() and the convenience functions for it.
*
- * \value CheckInterfaceSupported Don't return an interface instance unless it
- * can be guaranteed that the remote object
- * actually implements the interface.
- * \value BypassInterfaceCheck Return an interface instance even if it can't
- * be verified that the remote object supports the
- * interface.
* \sa optionalInterface()
*/
+/**
+ * \var DBusProxy::InterfaceSupportedChecking DBusProxy::CheckInterfaceSupported
+ * Don't return an interface instance unless it can be guaranteed that the
+ * remote object actually implements the interface.
+ */
+/**
+ * \var DBusProxy::InterfaceSupportedChecking DBusProxy::BypassInterfaceCheck
+ * Return an interface instance even if it can't be verified that the remote
+ * object supports the interface.
+ */
// Features in TpProxy but not here:
// * tracking which interfaces we have (in tpqt4, subclasses do that)
--
1.5.6.5
More information about the telepathy-commits
mailing list