X-Git-Url: https://git.saurik.com/wxWidgets.git/blobdiff_plain/2b5f62a0b2db198609b45dec622a018dae37008e..6d30807295d16ad7bddd2ef03b7dbf91a7a6335a:/docs/html/faqgtk.htm
diff --git a/docs/html/faqgtk.htm b/docs/html/faqgtk.htm
index df33965ef4..cc4b3748e6 100644
--- a/docs/html/faqgtk.htm
+++ b/docs/html/faqgtk.htm
@@ -2,7 +2,7 @@
-wxWindows 2 for GTK FAQ
+wxWidgets 2 for GTK FAQ
@@ -13,7 +13,7 @@
-wxWindows 2 for GTK FAQ
+wxWidgets 2 for GTK FAQ
|
@@ -21,30 +21,32 @@
-See also top-level FAQ page.
+See also top-level FAQ page
+and Unix FAQ page.
List of questions in this category
-
+
-wxWindows 2 for GTK is a port of wxWindows to the GTK+ toolkit,
-which is freely available for most flavours of Unix with X. wxWindows 2 for GTK is
+wxWidgets 2 for GTK is a port of wxWidgets to the GTK+ toolkit,
+which is freely available for most flavours of Unix with X. wxWidgets 2 for GTK is
often abbreviated to wxGTK. wxGTK has a separate home page here.
-
+
If your program reads the floating point numbers in the format 123.45
from a file, it may suddently start returning just 123 instead of the
@@ -74,7 +76,7 @@ future, probably as a separate library.
It seems that some versions of RedHat include a badly patched version of GTK+ (not wxGTK)
-which causes some trouble with wxWindows' socket code. Common symptoms are that when
+which causes some trouble with wxWidgets' socket code. Common symptoms are that when
a client tries to establish a connection to an existing server which refuses the request,
the client will get notified twice, first getting a LOST event and then a CONNECT event.
This problem can be solved by updating GTK with an official distribution of the library.
@@ -99,7 +101,7 @@ No, this is not possible. It leads to crashes in GTK+.
+EVT_CHAR not work?
In wxGTK, the frames never get focus and so can never receive CHAR
nor KEY events so an EVT_CHAR handler for a frame will be
@@ -109,6 +111,14 @@ frame.
+
+
+When a fatal X11 error occurs, the application quits with no stack trace.
+To find out where the problem is, put a breakpoint on g_log (b g_log
+in gdb).
+
+
+