X-Git-Url: https://git.saurik.com/wxWidgets.git/blobdiff_plain/b1c1e25bb1b7c4889ce1eafe31edc4c0bee23f67..c16ab217c12bfd8aed5e243ee9d7bd05ec9595c7:/docs/html/faqgtk.htm?ds=sidebyside
diff --git a/docs/html/faqgtk.htm b/docs/html/faqgtk.htm
index a7f7985a41..6da8b25c07 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,13 +21,14 @@
-See also top-level FAQ page.
+See also top-level FAQ page
+and Unix FAQ page.
List of questions in this category
-- What is wxWindows 2 for GTK+?
-- Why doesn't reading floating point numbers work when using wxWindows?
+- What is wxWidgets 2 for GTK+?
+- Why doesn't reading floating point numbers work when using wxWidgets?
- Does wxGTK have GNOME support?
- Warning about GTK libraries supplied with RedHat
- What range of Intel Linux platforms will a given application binary be usable on?
@@ -38,17 +39,17 @@ See also top-level FAQ page.
-
+
-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
+from a file, it may suddenly start returning just 123 instead of the
correct value on some systems -- which is all the more mysterious as the same
code in a standalone program works just fine.
@@ -75,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.