Include version-script.in in distributions
git-svn-id: https://svn.wxwidgets.org/svn/wx/wxWidgets/branches/WX_2_4_BRANCH@17985 c3d73ce0-8a6f-49c7-b76d-6d57e0e08775
This commit is contained in:
@@ -13,6 +13,7 @@ mkinstalldirs
|
||||
modules
|
||||
template.mak
|
||||
wx-config.in
|
||||
version-script.in
|
||||
setup.h_vms
|
||||
|
||||
distrib/msw/*.rsp
|
||||
|
@@ -32,6 +32,7 @@ See also <a href="faq.htm">top-level FAQ page</a>.
|
||||
<li><a href="#redhat">Warning about GTK libraries supplied with RedHat</a></li>
|
||||
<li><a href="#bincompat">What range of Intel Linux platforms will a given application binary be usable on?</a></li>
|
||||
<li><a href="#static">Can I statically link the GTK+ library?</a></li>
|
||||
<li><a href="#charinframe">Why does my simple program using <tt>EVT_CHAR</tt> doesn't work?</a></li>
|
||||
</ul>
|
||||
|
||||
<hr>
|
||||
@@ -97,6 +98,17 @@ the image libraries and std C++ lib)."
|
||||
No, this is not possible. It leads to crashes in GTK+.
|
||||
<P>
|
||||
|
||||
<h3><a name="#charinframe">Why does my simple program using
|
||||
<tt>EVT_CHAR</tt> doesn't work?</a></h3>
|
||||
|
||||
In wxGTK, the frames never get focus and so can never receive <tt>CHAR</tt>
|
||||
nor <tt>KEY</tt> events so an <tt>EVT_CHAR</tt> handler for a frame will be
|
||||
never called. To receive these events, you should create a <tt>wxPanel</tt>
|
||||
inside the frame and register the key event handlers for the panel, not the
|
||||
frame.
|
||||
|
||||
<p>
|
||||
|
||||
</font>
|
||||
|
||||
</BODY>
|
||||
|
@@ -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}$$}
|
||||
}}
|
||||
|
@@ -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}
|
||||
|
||||
|
Reference in New Issue
Block a user