summaryrefslogtreecommitdiff
path: root/docs/faq
diff options
context:
space:
mode:
authorMatthias Clasen <matthiasc@src.gnome.org>2003-07-23 18:58:48 +0000
committerMatthias Clasen <matthiasc@src.gnome.org>2003-07-23 18:58:48 +0000
commit1e6172147287073bcc0efafb59d4da1756ac4fdd (patch)
treea37637bbcc7d2d844b594fcc7b6b05f5ed158a98 /docs/faq
parent733f4489ade5b79227af871e1cbe694806ec367e (diff)
downloadgtk+-1e6172147287073bcc0efafb59d4da1756ac4fdd.tar.gz
Mention Xnest as a way to debug GTK+ apps.
* docs/faq/gtk-faq.sgml: Mention Xnest as a way to debug GTK+ apps.
Diffstat (limited to 'docs/faq')
-rw-r--r--docs/faq/gtk-faq.sgml13
1 files changed, 12 insertions, 1 deletions
diff --git a/docs/faq/gtk-faq.sgml b/docs/faq/gtk-faq.sgml
index e80bc9a79c..a31e3b5d74 100644
--- a/docs/faq/gtk-faq.sgml
+++ b/docs/faq/gtk-faq.sgml
@@ -838,7 +838,7 @@ way is to use the libglade library which directly loads
the XML user interface description files that Glade
generates into a running program.</para>
-Experienced GTK+ programmers generally strongly recommend
+<para>Experienced GTK+ programmers generally strongly recommend
using libglade; you don't have to worry about the interaction
between Glade generating the source and you editing it,
and its been shown to be a method that works better
@@ -1061,6 +1061,17 @@ port is also great for debugging X programs. Old vt100/vt220
terminals are dirt cheap but a bit hard to get (here in The
Netherlands, YMMV).</quote></para>
+<para>
+Another option is to run your application on Xnest. Xnest is an X server
+which displays its root window in a regular window of another X server.
+A pointer grab on the Xnest display will not affect the GUI of your debugger
+running on your regular X server.
+<programlisting>
+Xnest :1
+twm -display :1
+myapp --display=:1
+</programlisting>
+</para>
</sect1>
</chapter>