summaryrefslogtreecommitdiff
path: root/doc/src/howtos
diff options
context:
space:
mode:
authorJerome Pasion <jerome.pasion@digia.com>2013-05-06 17:30:46 +0200
committerThe Qt Project <gerrit-noreply@qt-project.org>2013-05-07 12:14:25 +0200
commite3e8118a701211404fac72e106f609cf82aaa1aa (patch)
treee19660c66a56369dfe375a29e4796df978faeea4 /doc/src/howtos
parentd88af017e7f216720f41efe19d39a54ca8c74ce3 (diff)
downloadqtdoc-e3e8118a701211404fac72e106f609cf82aaa1aa.tar.gz
Doc: Various changes to the platform related documentation.
-Removed "Cross-Platform and Platform-Specific Development" page. Our overviews are presumed to be cross-platform and the platform specific content are in the respective platform pages. The page adds no value to our doc architecture. -Removed group "platform-specific" group. It is not necessary as the platform pages already contains a link to their specific issues. I dispersed some of the links so then they are accessible from the platform pages. Change-Id: I1d7eef83b8d5f1dc5af7d4c61833875da636cc39 Reviewed-by: Martin Smith <martin.smith@digia.com> Reviewed-by: Leena Miettinen <riitta-leena.miettinen@digia.com> Reviewed-by: Sze Howe Koh <szehowe.koh@gmail.com>
Diffstat (limited to 'doc/src/howtos')
-rw-r--r--doc/src/howtos/unix-signal-handlers.qdoc3
1 files changed, 1 insertions, 2 deletions
diff --git a/doc/src/howtos/unix-signal-handlers.qdoc b/doc/src/howtos/unix-signal-handlers.qdoc
index 04248faf..16714d25 100644
--- a/doc/src/howtos/unix-signal-handlers.qdoc
+++ b/doc/src/howtos/unix-signal-handlers.qdoc
@@ -30,7 +30,6 @@
\title Calling Qt Functions From Unix Signal Handlers
\brief You can't. But don't despair, there is a way...
- \ingroup platform-specific
\ingroup best-practices
You \e can't call Qt functions from Unix signal handlers. The
@@ -58,7 +57,7 @@
SIGTERM signals. Note: You should read the socketpair(2) and the
sigaction(2) man pages before plowing through the following code
snippets.
-
+
\snippet doc/src/snippets/code/doc_src_unix-signal-handlers.cpp 0
In the MyDaemon constructor, use the socketpair(2) function to