X-Git-Url: https://git.saurik.com/wxWidgets.git/blobdiff_plain/4f3b37fd0e60dcdf61c951e3c220fe267e8257f8..05159a2750ed2cc5945a85bc5fc6849ad1a30e75:/docs/html/faqgtk.htm?ds=inline
diff --git a/docs/html/faqgtk.htm b/docs/html/faqgtk.htm
index c93ebad47e..df33965ef4 100644
--- a/docs/html/faqgtk.htm
+++ b/docs/html/faqgtk.htm
@@ -1,3 +1,4 @@
+
@@ -25,12 +26,13 @@ See also top-level FAQ page.
List of questions in this category
@@ -69,9 +71,9 @@ so may be added without dependence on libraries. Other features may be supported
future, probably as a separate library.
-
+
-It seems that some versions of RedHat include a badly patched version of GTK (not wxGTK)
+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
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.
@@ -89,6 +91,23 @@ and programs linked against it will not run with version
on a 2.1.X system. It will then run on practically all
Linux distros (if you link you app statically against
the image libraries and std C++ lib)."
+
+
+
+
+No, this is not possible. It leads to crashes in GTK+.
+
+
+
+
+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
+never called. To receive these events, you should create a wxPanel
+inside the frame and register the key event handlers for the panel, not the
+frame.
+
+