From 3b8e6027c2f79bde70f9415f0757df073ef75702 Mon Sep 17 00:00:00 2001 From: Casper van Donderen Date: Mon, 7 May 2012 14:03:02 +0200 Subject: Doc: Modularize QtDBus documentation and add missing file to QtNetwork. This change moves the snippets and images to the modularized directories. Change-Id: Idacff866735d00b048d65318bc4c3ee1dfa16310 Reviewed-by: Marius Storm-Olsen --- src/dbus/qdbuspendingreply.cpp | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) (limited to 'src/dbus/qdbuspendingreply.cpp') diff --git a/src/dbus/qdbuspendingreply.cpp b/src/dbus/qdbuspendingreply.cpp index b9694ca205..2fd219260d 100644 --- a/src/dbus/qdbuspendingreply.cpp +++ b/src/dbus/qdbuspendingreply.cpp @@ -69,22 +69,22 @@ Where with QDBusReply you would write: - \snippet doc/src/snippets/code/src_qdbus_qdbusreply.cpp 0 + \snippet code/src_qdbus_qdbusreply.cpp 0 with QDBusPendingReply, the equivalent code (including the blocking wait for the reply) would be: - \snippet doc/src/snippets/code/src.qdbus.qdbuspendingreply.cpp 0 + \snippet code/src_qdbus_qdbuspendingreply.cpp 0 For method calls that have more than one output argument, with QDBusReply, you would write: - \snippet doc/src/snippets/code/src_qdbus_qdbusreply.cpp 1 + \snippet code/src_qdbus_qdbusreply.cpp 1 whereas with QDBusPendingReply, all of the output arguments should be template parameters: - \snippet doc/src/snippets/code/src.qdbus.qdbuspendingreply.cpp 2 + \snippet code/src_qdbus_qdbuspendingreply.cpp 2 QDBusPendingReply objects can be associated with QDBusPendingCallWatcher objects, which emit signals when the reply -- cgit v1.2.3