diff --git a/distrib/msw/generic.rsp b/distrib/msw/generic.rsp index 7e61bcc925..ab022228b2 100644 --- a/distrib/msw/generic.rsp +++ b/distrib/msw/generic.rsp @@ -13,6 +13,7 @@ mkinstalldirs modules template.mak wx-config.in +version-script.in setup.h_vms distrib/msw/*.rsp diff --git a/docs/html/faqgtk.htm b/docs/html/faqgtk.htm index 3c78c002c6..df33965ef4 100644 --- a/docs/html/faqgtk.htm +++ b/docs/html/faqgtk.htm @@ -32,6 +32,7 @@ See also top-level FAQ page.
  • Warning about GTK libraries supplied with RedHat
  • What range of Intel Linux platforms will a given application binary be usable on?
  • Can I statically link the GTK+ library?
  • +
  • Why does my simple program using EVT_CHAR doesn't work?

  • @@ -97,6 +98,17 @@ the image libraries and std C++ lib)." No, this is not possible. It leads to crashes in GTK+.

    +

    Why does my simple program using +EVT_CHAR doesn't 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 +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. + +

    + diff --git a/docs/latex/wx/manual.tex b/docs/latex/wx/manual.tex index 24e50a9fde..91e3b2aa0e 100644 --- a/docs/latex/wx/manual.tex +++ b/docs/latex/wx/manual.tex @@ -26,7 +26,7 @@ %\special{!/@scaleunit 1 def} \parskip=10pt \parindent=0pt -\title{wxWindows 2.3: A portable C++ and Python GUI toolkit} +\title{wxWindows 2.3.4: A portable C++ and Python GUI toolkit} \winhelponly{\author{by Julian Smart et al %\winhelponly{\\$$\image{1cm;0cm}{wxwin.wmf}$$} }} diff --git a/docs/latex/wx/window.tex b/docs/latex/wx/window.tex index 999c1e63cc..c784cfbb04 100644 --- a/docs/latex/wx/window.tex +++ b/docs/latex/wx/window.tex @@ -3,13 +3,13 @@ wxWindow is the base class for all windows. Any children of the window will be deleted automatically by the destructor before the window itself is deleted. -Please note that we documented a number of handler functions (OnChar(), OnMouse() etc.) in this -help text. These must not be called by a user program and are documented only for illustration. -On several platforms, only a few of these handlers are actually written (they are not always -needed) and if you are uncertain on how to add a certain behaviour to a window class, intercept -the respective event as usual and call \helpref{wxEvent::Skip}{wxeventskip} so that the native -platform can implement its native behaviour or just ignore the event if nothing needs to be -done. +%Please note that we documented a number of handler functions (OnChar(), OnMouse() etc.) in this +%help text. These must not be called by a user program and are documented only for illustration. +%On several platforms, only a few of these handlers are actually written (they are not always +%needed) and if you are uncertain on how to add a certain behaviour to a window class, intercept +%the respective event as usual and call \helpref{wxEvent::Skip}{wxeventskip} so that the native +%platform can implement its native behaviour or just ignore the event if nothing needs to be +%done. \wxheading{Derived from}