Amebis/wxWidgets
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Name change replacements

Browse Source 
git-svn-id: https://svn.wxwidgets.org/svn/wx/wxWidgets/trunk@27090 c3d73ce0-8a6f-49c7-b76d-6d57e0e08775
This commit is contained in:
Julian Smart
2004-05-04 08:27:20 +00:00
parent e119d0498a
commit fc2171bd4c
268 changed files with 1372 additions and 1366 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
docs/latex/wx/accessible.tex
View File

@@ -5,10 +5,10 @@
\section{\class{wxAccessible}}\label{wxaccessible}
The wxAccessible class allows wxWindows applications, and
wxWindows itself, to return extended information about user interface elements
The wxAccessible class allows wxWidgets applications, and
wxWidgets itself, to return extended information about user interface elements
to client applications such as screen readers. This is the
main way in which wxWindows implements accessibility features.
main way in which wxWidgets implements accessibility features.
At present, only Microsoft Active Accessibility is supported
by this class.
@@ -32,7 +32,7 @@ wxAccessible; for example, the sash of a splitter window.
For details on the semantics of functions and types, please refer to the
Microsoft Active Accessibility 1.2 documentation.
This class is compiled into wxWindows only if the wxUSE\_ACCESSIBILITY setup
This class is compiled into wxWidgets only if the wxUSE\_ACCESSIBILITY setup
symbol is set to 1.
\wxheading{Derived from}

34
docs/latex/wx/app.tex
View File

@@ -12,7 +12,7 @@ objects in the application.
\end{itemize}
You should use the macro IMPLEMENT\_APP(appClass) in your application implementation
file to tell wxWindows how to create an instance of your application class.
file to tell wxWidgets how to create an instance of your application class.
Use DECLARE\_APP(appClass) in a header file if you want the wxGetApp function (which returns
a reference to your application object) to be visible to other files.
@@ -112,7 +112,7 @@ Returns the application name.
\wxheading{Remarks}
wxWindows sets this to a reasonable default before
wxWidgets sets this to a reasonable default before
calling \helpref{wxApp::OnInit}{wxapponinit}, but the application can reset it at will.
@@ -200,7 +200,7 @@ the top window.
\func{int}{MainLoop}{\void}
Called by wxWindows on creation of the application. Override this if you wish
Called by wxWidgets on creation of the application. Override this if you wish
to provide your own (environment-dependent) main loop.
\wxheading{Return value}
@@ -346,7 +346,7 @@ Finally note that if the exception is rethrown from here, it can be caught in
Override this member function for any processing which needs to be
done as the application is about to exit. OnExit is called after
destroying all application windows and controls, but before
wxWindows cleanup. Note that it is not called at all if
wxWidgets cleanup. Note that it is not called at all if
\helpref{OnInit}{wxapponinit} failed.
The return value of this function is currently ignored, return the same value
@@ -381,11 +381,11 @@ work and, in fact, probably won't.
%%since this forwards OnIdle events to windows and also performs garbage collection for
%%windows whose destruction has been delayed.
%%
%%wxWindows' strategy for OnIdle processing is as follows. After pending user interface events for an
%%application have all been processed, wxWindows sends an OnIdle event to the application object. wxApp::OnIdle itself
%%wxWidgets' strategy for OnIdle processing is as follows. After pending user interface events for an
%%application have all been processed, wxWidgets sends an OnIdle event to the application object. wxApp::OnIdle itself
%%sends an OnIdle event to each application window, allowing windows to do idle processing such as updating
%%their appearance. If either wxApp::OnIdle or a window OnIdle function requested more time, by
%%calling \helpref{wxIdleEvent::RequestMore}{wxidleeventrequestmore}, wxWindows will send another OnIdle
%%calling \helpref{wxIdleEvent::RequestMore}{wxidleeventrequestmore}, wxWidgets will send another OnIdle
%%event to the application object. This will occur in a loop until either a user event is found to be
%%pending, or OnIdle requests no more time. Then all pending user events are processed until the system
%%goes idle again, when OnIdle is called, and so on.
@@ -433,7 +433,7 @@ application's main window, optionally calling
that the function returns \true.
Notice that if you want to to use the command line processing provided by
wxWindows you have to call the base class version in the derived class
wxWidgets you have to call the base class version in the derived class
OnInit().
Return \true to continue processing, \false to exit the application
@@ -488,7 +488,7 @@ Under Windows, OnQueryEndSession is called in response to the WM\_QUERYENDSESSIO
\func{virtual int}{OnRun}{\void}
This virtual function is where the execution of a program written in wxWindows
This virtual function is where the execution of a program written in wxWidgets
starts. The default implementation just enters the main loop and starts
handling the events until it terminates, either because
\helpref{ExitMainLoop}{wxappexitmainloop} has been explicitly called or because
@@ -519,14 +519,14 @@ try/catch clause around the call to the base class version there.
Windows-only function for processing a message. This function
is called from the main message loop, checking for windows that
may wish to process it. The function returns true if the message
was processed, false otherwise. If you use wxWindows with another class
was processed, false otherwise. If you use wxWidgets with another class
library with its own message loop, you should make sure that this
function is called to allow wxWindows to receive messages. For example,
function is called to allow wxWidgets to receive messages. For example,
to allow co-existence with the Microsoft Foundation Classes, override
the PreTranslateMessage function:
\begin{verbatim}
// Provide wxWindows message loop compatibility
// Provide wxWidgets message loop compatibility
BOOL CTheApp::PreTranslateMessage(MSG *msg)
{
if (wxTheApp && wxTheApp->ProcessMessage((WXMSW *)msg))
@@ -554,7 +554,7 @@ Returns true if unprocessed events are in the window system event queue.
Sends idle events to a window and its children.
Please note that this function is internal to wxWindows and shouldn't be used
Please note that this function is internal to wxWidgets and shouldn't be used
by user code.
\wxheading{Remarks}
@@ -573,7 +573,7 @@ If true is returned, more OnIdle processing is requested by one or more window.
Sets the name of the application. The name may be used in dialogs
(for example by the document/view framework). A default name is set by
wxWindows.
wxWidgets.
\wxheading{See also}
@@ -635,10 +635,10 @@ deleted. If false, the application will continue to run.}
\func{void}{SetTopWindow}{\param{wxWindow* }{window}}
Sets the `top' window. You can call this from within \helpref{wxApp::OnInit}{wxapponinit} to
let wxWindows know which is the main window. You don't have to set the top window;
let wxWidgets know which is the main window. You don't have to set the top window;
it is only a convenience so that (for example) certain dialogs without parents can use a
specific window as the top window. If no top window is specified by the application,
wxWindows just uses the first frame or dialog in its top-level window list, when it
wxWidgets just uses the first frame or dialog in its top-level window list, when it
needs to use the top window.
\wxheading{Parameters}
@@ -657,7 +657,7 @@ needs to use the top window.
Sets the name of application's vendor. The name will be used
in registry access. A default name is set by
wxWindows.
wxWidgets.
\wxheading{See also}

14
docs/latex/wx/array.tex
View File

@@ -22,7 +22,7 @@ but the price is preallocating the memory in advance. In the \helpref{memory man
you may find some useful hints about optimizing wxArray memory usage. As for executable size, all
wxArray functions are inline, so they do not take {\it any space at all}.
wxWindows has three different kinds of array. All of them derive from
wxWidgets has three different kinds of array. All of them derive from
wxBaseArray class which works with untyped data and can not be used directly.
The standard macros WX\_DEFINE\_ARRAY(), WX\_DEFINE\_SORTED\_ARRAY() and
WX\_DEFINE\_OBJARRAY() are used to define a new class deriving from it. The
@@ -39,14 +39,14 @@ deleted when the element is removed from the array. It should be noted that
all of wxArray's functions are inline, so it costs strictly nothing to define as
many array types as you want (either in terms of the executable size or the
speed) as long as at least one of them is defined and this is always the case
because wxArrays are used by wxWindows internally. This class has one serious
because wxArrays are used by wxWidgets internally. This class has one serious
limitation: it can only be used for storing integral types (bool, char, short,
int, long and their unsigned variants) or pointers (of any kind). An attempt
to use with objects of sizeof() greater than sizeof(long) will provoke a
runtime assertion failure, however declaring a wxArray of floats will not (on
the machines where sizeof(float) <= sizeof(long)), yet it will {\bf not} work,
please use wxObjArray for storing floats and doubles (NB: a more efficient
wxArrayDouble class is scheduled for the next release of wxWindows).
wxArrayDouble class is scheduled for the next release of wxWidgets).
wxSortedArray is a wxArray variant which should be used when searching in the
array is a frequently used operation. It requires you to define an additional
@@ -248,7 +248,7 @@ does exactly the same as \helpref{Item()}{wxarrayitem} method.
\func{}{WX\_DEFINE\_USER\_EXPORTED\_ARRAY}{\param{}{T}, \param{}{name}, \param{}{exportspec}}
This macro defines a new array class named {\it name} and containing the
elements of type {\it T}. The second form is used when compiling wxWindows as
elements of type {\it T}. The second form is used when compiling wxWidgets as
a DLL under Windows and array needs to be visible outside the DLL. The third is
needed for exporting an array from a user DLL.
@@ -261,7 +261,7 @@ class MyClass;
WX_DEFINE_ARRAY(MyClass *, wxArrayOfMyClass);
\end{verbatim}
Note that wxWindows predefines the following standard array classes: wxArrayInt,
Note that wxWidgets predefines the following standard array classes: wxArrayInt,
wxArrayLong and wxArrayPtrVoid.
\membersection{WX\_DEFINE\_SORTED\_ARRAY}\label{wxdefinesortedarray}
@@ -273,7 +273,7 @@ wxArrayLong and wxArrayPtrVoid.
\func{}{WX\_DEFINE\_SORTED\_USER\_EXPORTED\_ARRAY}{\param{}{T}, \param{}{name}}
This macro defines a new sorted array class named {\it name} and containing
the elements of type {\it T}. The second form is used when compiling wxWindows as
the elements of type {\it T}. The second form is used when compiling wxWidgets as
a DLL under Windows and array needs to be visible outside the DLL. The third is
needed for exporting an array from a user DLL.
@@ -315,7 +315,7 @@ wxArrayOfMyClass another(CompareMyClassObjects);
\func{}{WX\_DECLARE\_USER\_EXPORTED\_OBJARRAY}{\param{}{T}, \param{}{name}}
This macro declares a new object array class named {\it name} and containing
the elements of type {\it T}. The second form is used when compiling wxWindows as
the elements of type {\it T}. The second form is used when compiling wxWidgets as
a DLL under Windows and array needs to be visible outside the DLL. The third is
needed for exporting an array from a user DLL.

6
docs/latex/wx/artprov.tex
View File

@@ -5,8 +5,8 @@
\section{\class{wxArtProvider}}\label{wxartprovider}
wxArtProvider class is used to customize the look of wxWindows application.
When wxWindows need to display an icon or a bitmap (e.g. in the standard file
wxArtProvider class is used to customize the look of wxWidgets application.
When wxWidgets need to display an icon or a bitmap (e.g. in the standard file
dialog), it does not use hard-coded resource but asks wxArtProvider for it
instead. This way the users can plug in own wxArtProvider class and easily
replace standard art with his/her own version. It is easy thing to do: all
@@ -32,7 +32,7 @@ There's another way of taking advantage of this class: you can use it in your co
platform native icons as provided by
\helpref{wxArtProvider::GetBitmap}{wxartprovidergetbitmap} or
\helpref{wxArtProvider::GetIcon}{wxartprovidergeticon} (NB: this is not yet really
possible as of wxWindows 2.3.3, the set of wxArtProvider bitmaps is too
possible as of wxWidgets 2.3.3, the set of wxArtProvider bitmaps is too
small).
\membersection{Identifying art resources}

4
docs/latex/wx/bbutton.tex
View File

@@ -18,7 +18,7 @@ almost any other window.
\wxheading{Remarks}
A bitmap button can be supplied with a single bitmap, and wxWindows will draw
A bitmap button can be supplied with a single bitmap, and wxWidgets will draw
all button states using this bitmap. If the application needs more control, additional bitmaps for
the selected state, unpressed focused state, and greyed-out state may be supplied.
@@ -91,7 +91,7 @@ appropriately for the bitmap.}
\wxheading{Remarks}
The {\it bitmap} parameter is normally the only bitmap you need to provide, and wxWindows will
The {\it bitmap} parameter is normally the only bitmap you need to provide, and wxWidgets will
draw the button correctly in its different states. If you want more control, call
any of the functions \helpref{wxBitmapButton::SetBitmapSelected}{wxbitmapbuttonsetbitmapselected},\rtfsp
\helpref{wxBitmapButton::SetBitmapFocus}{wxbitmapbuttonsetbitmapfocus},\rtfsp

20
docs/latex/wx/bitmap.tex
View File

@@ -117,8 +117,8 @@ Its meaning is determined by the {\it type} parameter.}
\twocolitem{\indexit{wxBITMAP\_TYPE\_RESOURCE}}{Load a Windows resource name.}
\end{twocollist}
The validity of these flags depends on the platform and wxWindows configuration.
If all possible wxWindows settings are used, the Windows platform supports BMP file, BMP resource,
The validity of these flags depends on the platform and wxWidgets configuration.
If all possible wxWidgets settings are used, the Windows platform supports BMP file, BMP resource,
XPM data, and XPM. Under wxGTK, the available formats are BMP file, XPM data, XPM file, and PNG file.
Under wxMotif, the available formats are XBM data, XBM file, XPM data, XPM file.
@@ -145,7 +145,7 @@ X and Windows.
The sixth form constructs a new bitmap.
The seventh form constructs a bitmap from pixmap (XPM) data, if wxWindows has been configured
The seventh form constructs a bitmap from pixmap (XPM) data, if wxWidgets has been configured
to incorporate this feature.
To use this constructor, you must first include an XPM file. For
@@ -205,7 +205,7 @@ destroyed at this point - only when the reference count is zero will the
data be deleted.
If the application omits to delete the bitmap explicitly, the bitmap will be
destroyed automatically by wxWindows when the application exits.
destroyed automatically by wxWidgets when the application exits.
Do not delete a bitmap that is selected into a memory device context.
@@ -228,7 +228,7 @@ of a given handler class in an application session.}
Deletes all bitmap handlers.
This function is called by wxWindows on exit.
This function is called by wxWidgets on exit.
\membersection{wxBitmap::ConvertToImage}\label{wxbitmapconverttoimage}
@@ -375,10 +375,10 @@ the bitmap. This function preserves bit depth and mask information.
\func{static void}{InitStandardHandlers}{\void}
Adds the standard bitmap format handlers, which, depending on wxWindows
Adds the standard bitmap format handlers, which, depending on wxWidgets
configuration, can be handlers for Windows bitmap, Windows bitmap resource, and XPM.
This function is called by wxWindows on startup.
This function is called by wxWidgets on startup.
\wxheading{See also}
@@ -419,7 +419,7 @@ The meaning of {\it name} is determined by the {\it type} parameter.}
\twocolitem{{\bf wxBITMAP\_TYPE\_XPM}}{Load an XPM bitmap file.}
\end{twocollist}
The validity of these flags depends on the platform and wxWindows configuration.
The validity of these flags depends on the platform and wxWidgets configuration.
In addition, wxBitmap can read all formats that \helpref{wxImage}{wximage} can
(wxBITMAP\_TYPE\_JPEG, wxBITMAP\_TYPE\_PNG, wxBITMAP\_TYPE\_GIF, wxBITMAP\_TYPE\_PCX, wxBITMAP\_TYPE\_PNM).
@@ -482,7 +482,7 @@ Saves a bitmap in the named file.
\twocolitem{{\bf wxBITMAP\_TYPE\_XPM}}{Save an XPM bitmap file.}
\end{twocollist}
The validity of these flags depends on the platform and wxWindows configuration.
The validity of these flags depends on the platform and wxWidgets configuration.
In addition, wxBitmap can save all formats that \helpref{wxImage}{wximage} can
(wxBITMAP\_TYPE\_JPEG, wxBITMAP\_TYPE\_PNG).
@@ -498,7 +498,7 @@ true if the operation succeeded, false otherwise.
\wxheading{Remarks}
Depending on how wxWindows has been configured, not all formats may be available.
Depending on how wxWidgets has been configured, not all formats may be available.
\wxheading{See also}

2
docs/latex/wx/bmpdatob.tex
View File

@@ -47,7 +47,7 @@ Constructor, optionally passing a bitmap (otherwise use
Returns the bitmap associated with the data object. You may wish to override
this method when offering data on-demand, but this is not required by
wxWindows' internals. Use this method to get data in bitmap form from
wxWidgets' internals. Use this method to get data in bitmap form from
the \helpref{wxClipboard}{wxclipboard}.
\membersection{wxBitmapDataObject::SetBitmap}\label{wxbitmapdataobjectsetbitmap}

140
docs/latex/wx/body.tex
View File

@@ -3,21 +3,21 @@
\setheader{{\it CHAPTER \thechapter}}{}{}{}{}{{\it CHAPTER \thechapter}}%
\setfooter{\thepage}{}{}{}{}{\thepage}%
\section{What is wxWindows?}
\section{What is wxWidgets?}
wxWindows is a C++ framework providing GUI (Graphical User
wxWidgets is a C++ framework providing GUI (Graphical User
Interface) and other facilities on more than one platform. Version 2 currently
supports all desktop versions of MS Windows, Unix with GTK+, Unix with Motif,
and MacOS. An OS/2 port is in progress.
wxWindows was originally developed at the Artificial Intelligence
wxWidgets was originally developed at the Artificial Intelligence
Applications Institute, University of Edinburgh, for internal use,
and was first made publicly available in 1992.
Version 2 is a vastly improved version written and maintained by
Julian Smart, Robert Roebling, Vadim Zeitlin, Vaclav Slavik and many others.
This manual contains a class reference and topic overviews.
For a selection of wxWindows tutorials, please see the documentation page on the \urlref{wxWindows web site}{http://www.wxwindows.org}.
For a selection of wxWidgets tutorials, please see the documentation page on the \urlref{wxWidgets web site}{http://www.wxwidgets.org}.
Please note that in the following, ``MS Windows" often refers to all
platforms related to Microsoft Windows, including 16-bit and 32-bit
@@ -25,7 +25,7 @@ variants, unless otherwise stated. All trademarks are acknowledged.
\section{Why another cross-platform development tool?}
wxWindows was developed to provide a cheap and flexible way to maximize
wxWidgets was developed to provide a cheap and flexible way to maximize
investment in GUI application development. While a number of commercial
class libraries already existed for cross-platform development,
none met all of the following criteria:
@@ -37,14 +37,14 @@ none met all of the following criteria:
\item support for a wide range of compilers.
\end{enumerate}
Since wxWindows was started, several other free or almost-free
Since wxWidgets was started, several other free or almost-free
GUI frameworks have emerged. However, none has the range of
features, flexibility, documentation and the well-established
development team that wxWindows has.
development team that wxWidgets has.
As open source software, wxWindows has benefited from comments,
As open source software, wxWidgets has benefited from comments,
ideas, bug fixes, enhancements and the sheer enthusiasm of
users. This gives wxWindows a certain advantage over its
users. This gives wxWidgets a certain advantage over its
commercial competitors (and over free libraries without an
independent development team), plus a robustness against the
transience of one individual or company. This openness and
@@ -61,19 +61,19 @@ The importance of using a platform-independent class library
cannot be overstated, since GUI application development is very
time-consuming, and sustained popularity of particular GUIs
cannot be guaranteed. Code can very quickly become obsolete if
it addresses the wrong platform or audience. wxWindows helps to
it addresses the wrong platform or audience. wxWidgets helps to
insulate the programmer from these winds of change. Although
wxWindows may not be suitable for every application (such as an
wxWidgets may not be suitable for every application (such as an
OLE-intensive program), it provides access to most of the
functionality a GUI program normally requires, plus many extras
such as network programming, PostScript output, and HTML
rendering; and it can of course be extended as needs dictate.
As a bonus, it provides a far cleaner and easier programming
interface than the native APIs. Programmers may find it
worthwhile to use wxWindows even if they are developing on only
worthwhile to use wxWidgets even if they are developing on only
one platform.
It is impossible to sum up the functionality of wxWindows in a few paragraphs, but
It is impossible to sum up the functionality of wxWidgets in a few paragraphs, but
here are some of the benefits:
\begin{itemize}\itemsep=0pt
@@ -134,9 +134,9 @@ Additions and changes:
\end{itemize}
\end{comment}
\section{wxWindows requirements}\label{requirements}
\section{wxWidgets requirements}\label{requirements}
To make use of wxWindows, you currently need one of the following setups.
To make use of wxWidgets, you currently need one of the following setups.
(a) MS-Windows:
@@ -166,22 +166,22 @@ If using the wxX11 port, no such widget set is required.
\item At least 60 MB of disk space.
\end{enumerate}
\section{Availability and location of wxWindows}
\section{Availability and location of wxWidgets}
\winhelponly{wxWindows is available by anonymous FTP and World Wide Web
from ftp://biolpc22.york.ac.uk/pub and/or http://www.wxwindows.org.}
\winhelpignore{wxWindows is available by anonymous FTP and World Wide Web
\winhelponly{wxWidgets is available by anonymous FTP and World Wide Web
from ftp://biolpc22.york.ac.uk/pub and/or http://www.wxwidgets.org.}
\winhelpignore{wxWidgets is available by anonymous FTP and World Wide Web
from \urlref{ftp://biolpc22.york.ac.uk/pub}{ftp://biolpc22.york.ac.uk/pub}
and/or \urlref{http://www.wxwindows.org}{http://www.wxwindows.org}.}
and/or \urlref{http://www.wxwidgets.org}{http://www.wxwidgets.org}.}
You can also buy a CD-ROM using the form on the Web site.
\section{Acknowledgements}
Thanks are due to AIAI for being willing to release the original version of
wxWindows into the public domain, and to our patient partners.
wxWidgets into the public domain, and to our patient partners.
We would particularly like to thank the following for their contributions to wxWindows, and the many others who have been involved in
We would particularly like to thank the following for their contributions to wxWidgets, and the many others who have been involved in
the project over the years. Apologies for any unintentional omissions from this list.
Yiorgos Adamopoulos, Jamshid Afshar, Alejandro Aguilar-Sierra, AIAI, Patrick Albert, Karsten Ballueder, Michael Bedward, Kai Bendorf, Yura Bidus, Keith
@@ -212,18 +212,18 @@ written prior permission. M.I.T. makes no representations about the
suitability of this software for any purpose. It is provided ``as is''
without express or implied warranty.}
\chapter{Multi-platform development with wxWindows}\label{multiplat}
\chapter{Multi-platform development with wxWidgets}\label{multiplat}
\setheader{{\it CHAPTER \thechapter}}{}{}{}{}{{\it CHAPTER \thechapter}}%
\setfooter{\thepage}{}{}{}{}{\thepage}%
This chapter describes the practical details of using wxWindows. Please
This chapter describes the practical details of using wxWidgets. Please
see the file install.txt for up-to-date installation instructions, and
changes.txt for differences between versions.
\section{Include files}
The main include file is {\tt "wx/wx.h"}; this includes the most commonly
used modules of wxWindows.
used modules of wxWidgets.
To save on compilation time, include only those header files relevant to the
source file. If you are using precompiled headers, you should include
@@ -254,40 +254,40 @@ Borland precompilation is largely automatic. Visual C++ requires specification o
the file to use for precompilation. Watcom C++ is automatic apart from the specification of
the .pch file. Watcom C++ is strange in requiring the precompiled header to be used only for
object files compiled in the same directory as that in which the precompiled header was created.
Therefore, the wxWindows Watcom C++ makefiles go through hoops deleting and recreating
Therefore, the wxWidgets Watcom C++ makefiles go through hoops deleting and recreating
a single precompiled header file for each module, thus preventing an accumulation of many
multi-megabyte .pch files.
\section{Libraries}
Most ports of wxWindows can create either a static library or a shared
library. wxWindows can also be built in multilib and monolithic variants.
Most ports of wxWidgets can create either a static library or a shared
library. wxWidgets can also be built in multilib and monolithic variants.
See the \helpref{libraries list}{librarieslist} for more
information on these.
\section{Configuration}
When using project files and makefiles directly to build wxWindows,
When using project files and makefiles directly to build wxWidgets,
options are configurable in the file
\rtfsp{\tt "wx/XXX/setup.h"} where XXX is the required platform (such as msw, motif, gtk, mac). Some
settings are a matter of taste, some help with platform-specific problems, and
others can be set to minimize the size of the library. Please see the setup.h file
and {\tt install.txt} files for details on configuration.
When using the 'configure' script to configure wxWindows (on Unix and other platforms where
When using the 'configure' script to configure wxWidgets (on Unix and other platforms where
configure is available), the corresponding setup.h files are generated automatically
along with suitable makefiles. When using the RPM packages
for installing wxWindows on Linux, a correct setup.h is shipped in the package and
for installing wxWidgets on Linux, a correct setup.h is shipped in the package and
this must not be changed.
\section{Makefiles}
On Microsoft Windows, wxWindows has a different set of makefiles for each
On Microsoft Windows, wxWidgets has a different set of makefiles for each
compiler, because each compiler's 'make' tool is slightly different.
Popular Windows compilers that we cater for, and the corresponding makefile
extensions, include: Microsoft Visual C++ (.vc), Borland C++ (.bcc),
OpenWatcom C++ (.wat) and MinGW/Cygwin (.gcc). Makefiles are provided
for the wxWindows library itself, samples, demos, and utilities.
for the wxWidgets library itself, samples, demos, and utilities.
On Linux, Mac and OS/2, you use the 'configure' command to
generate the necessary makefiles. You should also use this method when
@@ -295,15 +295,15 @@ building with MinGW/Cygwin on Windows.
We also provide project files for some compilers, such as
Microsoft VC++. However, we recommend using makefiles
to build the wxWindows library itself, because makefiles
to build the wxWidgets library itself, because makefiles
can be more powerful and less manual intervention is required.
On Windows using a compiler other than MinGW/Cygwin, you would
build the wxWindows library from the build/msw directory
build the wxWidgets library from the build/msw directory
which contains the relevant makefiles.
On Windows using MinGW/Cygwin, and on Unix, MacOS X and OS/2, you invoke
'configure' (found in the top-level of the wxWindows source hierarchy),
'configure' (found in the top-level of the wxWidgets source hierarchy),
from within a suitable empty directory for containing makefiles, object files and
libraries.
@@ -313,7 +313,7 @@ xxx is the platform of interest, such as msw, gtk, x11, mac.
\section{Windows-specific files}
wxWindows application compilation under MS Windows requires at least two
wxWidgets application compilation under MS Windows requires at least two
extra files, resource and module definition files.
\subsection{Resource file}\label{resources}
@@ -325,7 +325,7 @@ is the following statement:
#include "wx/msw/wx.rc"
\end{verbatim}
which includes essential internal wxWindows definitions. The resource script
which includes essential internal wxWidgets definitions. The resource script
may also contain references to icons, cursors, etc., for example:
\begin{verbatim}
@@ -339,7 +339,7 @@ the MS Windows SDK documentation.
so programs that search your executable for icons (such
as the Program Manager) find your application icon first.}
\section{Allocating and deleting wxWindows objects}
\section{Allocating and deleting wxWidgets objects}
In general, classes derived from wxWindow must dynamically allocated
with {\it new} and deleted with {\it delete}. If you delete a window,
@@ -347,7 +347,7 @@ all of its children and descendants will be automatically deleted,
so you don't need to delete these descendants explicitly.
When deleting a frame or dialog, use {\bf Destroy} rather than {\bf delete} so
that the wxWindows delayed deletion can take effect. This waits until idle time
that the wxWidgets delayed deletion can take effect. This waits until idle time
(when all messages have been processed) to actually delete the window, to avoid
problems associated with the GUI sending events to deleted windows.
@@ -355,8 +355,8 @@ Don't create a window on the stack, because this will interfere
with delayed deletion.
If you decide to allocate a C++ array of objects (such as wxBitmap) that may
be cleaned up by wxWindows, make sure you delete the array explicitly
before wxWindows has a chance to do so on exit, since calling {\it delete} on
be cleaned up by wxWidgets, make sure you delete the array explicitly
before wxWidgets has a chance to do so on exit, since calling {\it delete} on
array members will cause memory problems.
wxColour can be created statically: it is not automatically cleaned
@@ -375,7 +375,7 @@ A problem which sometimes arises from writing multi-platform programs is that
the basic C types are not defined the same on all platforms. This holds true
for both the length in bits of the standard types (such as int and long) as
well as their byte order, which might be little endian (typically
on Intel computers) or big endian (typically on some Unix workstations). wxWindows
on Intel computers) or big endian (typically on some Unix workstations). wxWidgets
defines types and macros that make it easy to write architecture independent
code. The types are:
@@ -391,7 +391,7 @@ are described in the \helpref{Byte order macros}{byteordermacros} section.
\section{Conditional compilation}
One of the purposes of wxWindows is to reduce the need for conditional
One of the purposes of wxWidgets is to reduce the need for conditional
compilation in source code, which can be messy and confusing to follow.
However, sometimes it is necessary to incorporate platform-specific
features (such as metafile use under MS Windows). The symbols
@@ -404,12 +404,12 @@ The following documents some miscellaneous C++ issues.
\subsection{Templates}
wxWindows does not use templates (except for some advanced features that
wxWidgets does not use templates (except for some advanced features that
are switched off by default) since it is a notoriously unportable feature.
\subsection{RTTI}
wxWindows does not use C++ run-time type information since wxWindows provides
wxWidgets does not use C++ run-time type information since wxWidgets provides
its own run-time type information system, implemented using macros.
\subsection{Type of NULL}
@@ -425,7 +425,7 @@ as
\end{verbatim}
}%
It is recommended to adhere to this in all code using wxWindows as
It is recommended to adhere to this in all code using wxWidgets as
this make the code (a bit) more portable.
\subsection{Precompiled headers}
@@ -433,8 +433,8 @@ this make the code (a bit) more portable.
Some compilers, such as Borland C++ and Microsoft C++, support
precompiled headers. This can save a great deal of compiling time. The
recommended approach is to precompile {\tt "wx.h"}, using this
precompiled header for compiling both wxWindows itself and any
wxWindows applications. For Windows compilers, two dummy source files
precompiled header for compiling both wxWidgets itself and any
wxWidgets applications. For Windows compilers, two dummy source files
are provided (one for normal applications and one for creating DLLs)
to allow initial creation of the precompiled header.
@@ -442,7 +442,7 @@ However, there are several downsides to using precompiled headers. One
is that to take advantage of the facility, you often need to include
more header files than would normally be the case. This means that
changing a header file will cause more recompilations (in the case of
wxWindows, everything needs to be recompiled since everything includes {\tt "wx.h"}!)
wxWidgets, everything needs to be recompiled since everything includes {\tt "wx.h"}!)
A related problem is that for compilers that don't have precompiled
headers, including a lot of header files slows down compilation
@@ -484,33 +484,33 @@ dos2unix).
See also the File Functions section of the reference manual for
descriptions of miscellaneous file handling functions.
\chapter{Utilities and libraries supplied with wxWindows}\label{utilities}
\chapter{Utilities and libraries supplied with wxWidgets}\label{utilities}
\setheader{{\it CHAPTER \thechapter}}{}{}{}{}{{\it CHAPTER \thechapter}}%
\setfooter{\thepage}{}{}{}{}{\thepage}%
In addition to the core wxWindows library, a number of further
In addition to the core wxWidgets library, a number of further
libraries and utilities are supplied with each distribution.
Some are under the 'contrib' hierarchy which mirrors the
structure of the main wxWindows hierarchy. See also the 'utils'
structure of the main wxWidgets hierarchy. See also the 'utils'
hierarchy. The first place to look for documentation about
these tools and libraries is under the wxWindows 'docs' hierarchy,
these tools and libraries is under the wxWidgets 'docs' hierarchy,
for example {\tt docs/htmlhelp/fl.chm}.
For other user-contributed packages, please see the Contributions page
on the \urlref{wxWindows Web site}{http://www.wxwindows.org}.
on the \urlref{wxWidgets Web site}{http://www.wxwidgets.org}.
\begin{description}\itemsep=0pt
\item[{\bf Helpview}]
Helpview is a program for displaying wxWindows HTML
Help files. In many cases, you may wish to use the wxWindows HTML
Helpview is a program for displaying wxWidgets HTML
Help files. In many cases, you may wish to use the wxWidgets HTML
Help classes from within your application, but this provides a
handy stand-alone viewer. See \helpref{wxHTML Notes}{wxhtml} for more details.
You can find it in {\tt samples/html/helpview}.
\item[{\bf Tex2RTF}]
Supplied with wxWindows is a utility called Tex2RTF for converting\rtfsp
Supplied with wxWidgets is a utility called Tex2RTF for converting\rtfsp
\LaTeX\ manuals HTML, MS HTML Help, wxHTML Help, RTF, and Windows
Help RTF formats. Tex2RTF is used for the wxWindows manuals and can be used independently
Help RTF formats. Tex2RTF is used for the wxWidgets manuals and can be used independently
by authors wishing to create on-line and printed manuals from the same\rtfsp
\LaTeX\ source. Please see the separate documentation for Tex2RTF.
You can find it under {\tt utils/tex2rtf}.
@@ -524,8 +524,8 @@ Xnest-based display emulator for X11-based PDA applications. On some
systems, the Xnest window does not synchronise with the
'skin' window. This program can be found in {\tt utils/emulator}.
\item[{\bf Configuration Tool}]
The wxWindows Configuration Tool is a work in progress
intended to make it easier to configure wxWindows
The wxWidgets Configuration Tool is a work in progress
intended to make it easier to configure wxWidgets
features in detail. It exports setup.h configurations and will
eventually generate makefile config files. Invoking compilers is
also on the cards. Since configurations are
@@ -572,17 +572,17 @@ You can find this in {\tt contrib/src/plot}, {\tt contrib/include/wx/plot}, and
\setfooter{\thepage}{}{}{}{}{\thepage}%
This chapter is intended to list strategies that may be useful when
writing and debugging wxWindows programs. If you have any good tips,
writing and debugging wxWidgets programs. If you have any good tips,
please submit them for inclusion here.
\section{Strategies for reducing programming errors}
\subsection{Use ASSERT}
Although I haven't done this myself within wxWindows, it is good
Although I haven't done this myself within wxWidgets, it is good
practice to use ASSERT statements liberally, that check for conditions that
should or should not hold, and print out appropriate error messages.
These can be compiled out of a non-debugging version of wxWindows
These can be compiled out of a non-debugging version of wxWidgets
and your application. Using ASSERT is an example of `defensive programming':
it can alert you to problems later on.
@@ -606,13 +606,13 @@ Don't use absolute panel item positioning if you can avoid it. Different GUIs ha
very differently sized panel items. Consider using the constraint system, although this
can be complex to program.
Alternatively, you could use alternative .wrc (wxWindows resource files) on different
Alternatively, you could use alternative .wrc (wxWidgets resource files) on different
platforms, with slightly different dimensions in each. Or space your panel items out
to avoid problems.
\subsection{Use wxWindows resource files}
\subsection{Use wxWidgets resource files}
Use .xrc (wxWindows resource files) where possible, because they can be easily changed
Use .xrc (wxWidgets resource files) where possible, because they can be easily changed
independently of source code.
\section{Strategies for debugging}\label{debugstrategies}
@@ -660,11 +660,11 @@ Using tracing statements may be more convenient than using the debugger
in some circumstances (such as when your debugger doesn't support a lot
of debugging code, or you wish to print a bunch of variables).
\subsection{Use the wxWindows debugging facilities}
\subsection{Use the wxWidgets debugging facilities}
You can use wxDebugContext to check for
memory leaks and corrupt memory: in fact in debugging mode, wxWindows will
automatically check for memory leaks at the end of the program if wxWindows is suitably
memory leaks and corrupt memory: in fact in debugging mode, wxWidgets will
automatically check for memory leaks at the end of the program if wxWidgets is suitably
configured. Depending on the operating system and compiler, more or less
specific information about the problem will be logged.

14
docs/latex/wx/brush.tex
View File

@@ -34,7 +34,7 @@ wxRED\_BRUSH}
\wxheading{Remarks}
On a monochrome display, wxWindows shows
On a monochrome display, wxWidgets shows
all brushes as white unless the colour is really black.
Do not initialize objects on the stack before the program commences,
@@ -130,7 +130,7 @@ system, since wxBrush uses a reference counting system for efficiency.
Although all remaining brushes are deleted when the application exits,
the application should try to clean up all brushes itself. This is because
wxWindows cannot know if a pointer to the brush object is stored in an
wxWidgets cannot know if a pointer to the brush object is stored in an
application data structure, and there is a risk of double deletion.
\membersection{wxBrush::GetColour}\label{wxbrushgetcolour}
@@ -304,7 +304,7 @@ be deleted and their resources freed, eliminating the possibility of
`memory leaks'. However, it is best not to rely on this automatic
cleanup because it can lead to double deletion in some circumstances.
There are two mechanisms in recent versions of wxWindows which make the
There are two mechanisms in recent versions of wxWidgets which make the
brush list less useful than it once was. Under Windows, scarce resources
are cleaned up internally if they are not being used. Also, a referencing
counting mechanism applied to all GDI objects means that some sharing
@@ -318,9 +318,9 @@ and copy brushes as you see fit. If your Windows resource meter suggests
your application is using too many resources, you can resort to using
GDI lists to share objects explicitly.
The only compelling use for the brush list is for wxWindows to keep
The only compelling use for the brush list is for wxWidgets to keep
track of brushes in order to clean them up on exit. It is also kept for
backward compatibility with earlier versions of wxWindows.
backward compatibility with earlier versions of wxWidgets.
\wxheading{See also}
@@ -339,7 +339,7 @@ use the object pointer {\bf wxTheBrushList}.
\func{void}{AddBrush}{\param{wxBrush *}{brush}}
Used internally by wxWindows to add a brush to the list.
Used internally by wxWidgets to add a brush to the list.
\membersection{wxBrushList::FindOrCreateBrush}\label{wxbrushlistfindorcreatebrush}
@@ -367,6 +367,6 @@ Finds a brush of the given specification, or creates one and adds it to the list
\func{void}{RemoveBrush}{\param{wxBrush *}{brush}}
Used by wxWindows to remove a brush from the list.
Used by wxWidgets to remove a brush from the list.

2
docs/latex/wx/bufferdc.tex
View File

@@ -6,7 +6,7 @@
%% Created: 07.02.04
%% RCS-ID: $Id$
%% Copyright: (c) 2004 Vadim Zeitlin
%% License: wxWindows license
%% License: wxWidgets license
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\section{\class{wxBufferedDC}}\label{wxbuffereddc}

2
docs/latex/wx/button.tex
View File

@@ -134,7 +134,7 @@ Note that under Motif, calling this function immediately after
creation of a button and before the creation of other buttons
will cause misalignment of the row of buttons, since default
buttons are larger. To get around this, call {\it SetDefault}\rtfsp
after you have created a row of buttons: wxWindows will
after you have created a row of buttons: wxWidgets will
then set the size of all buttons currently on the panel to
the same size.

2
docs/latex/wx/calctrl.tex
View File

@@ -6,7 +6,7 @@
%% Created: 03.01.00
%% RCS-ID: $Id$
%% Copyright: (c) Vadim Zeitlin
%% License: wxWindows license
%% License: wxWidgets license
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\section{\class{wxCalendarCtrl}}\label{wxcalendarctrl}

2
docs/latex/wx/caret.tex
View File

@@ -6,7 +6,7 @@
%% Created: 20.06.00
%% RCS-ID: $Id$
%% Copyright: (c) Vadim Zeitlin
%% License: wxWindows license
%% License: wxWidgets license
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\section{\class{wxCaret}}\label{wxcaret}

30
docs/latex/wx/category.tex
View File

@@ -2,7 +2,7 @@
\setheader{{\it CHAPTER \thechapter}}{}{}{}{}{{\it CHAPTER \thechapter}}%
\setfooter{\thepage}{}{}{}{}{\thepage}%
A classification of wxWindows classes by category.
A classification of wxWidgets classes by category.
{\large {\bf Managed windows}}
@@ -267,7 +267,7 @@ user input.
{\large {\bf Data structures}}
These are the data structure classes supported by wxWindows.
These are the data structure classes supported by wxWidgets.
\twocolwidtha{6cm}
\begin{twocollist}\itemsep=0pt
@@ -282,7 +282,7 @@ These are the data structure classes supported by wxWindows.
\twocolitem{\helpref{wxList}{wxlist}}{A simple linked list implementation}
\twocolitem{\helpref{wxLongLong}{wxlonglong}}{A portable 64 bit integer type}
\twocolitem{\helpref{wxNode}{wxnode}}{Represents a node in the wxList implementation}
\twocolitem{\helpref{wxObject}{wxobject}}{The root class for most wxWindows classes}
\twocolitem{\helpref{wxObject}{wxobject}}{The root class for most wxWidgets classes}
\twocolitem{\helpref{wxPathList}{wxpathlist}}{A class to help search multiple paths}
\twocolitem{\helpref{wxPoint}{wxpoint}}{Representation of a point}
\twocolitem{\helpref{wxRect}{wxrect}}{A class representing a rectangle}
@@ -301,7 +301,7 @@ These are the data structure classes supported by wxWindows.
\overview{Overview}{runtimeclassoverview}
wxWindows supports run-time manipulation of class information, and dynamic
wxWidgets supports run-time manipulation of class information, and dynamic
creation of objects given class names.
\twocolwidtha{6cm}
@@ -315,7 +315,7 @@ creation of objects given class names.
\overview{Overview}{wxlogoverview}
wxWindows provides several classes and functions for message logging.
wxWidgets provides several classes and functions for message logging.
Please see the \helpref{wxLog overview}{wxlogoverview} for more details.
\twocolwidtha{6cm}
@@ -338,7 +338,7 @@ to redirect output sent to {\tt cout} to a \helpref{wxTextCtrl}{wxtextctrl}}
\overview{Overview}{debuggingoverview}
wxWindows supports some aspects of debugging an application through
wxWidgets supports some aspects of debugging an application through
classes, functions and macros.
\twocolwidtha{6cm}
@@ -353,7 +353,7 @@ classes, functions and macros.
{\large {\bf Networking classes}}
wxWindows provides its own classes for socket based networking.
wxWidgets provides its own classes for socket based networking.
\twocolwidtha{6cm}
\begin{twocollist}\itemsep=0pt
@@ -374,7 +374,7 @@ wxWindows provides its own classes for socket based networking.
\overview{Overview}{ipcoverview}
wxWindows provides simple interprocess communications facilities
wxWidgets provides simple interprocess communications facilities
based on Windows DDE, but available on most platforms using TCP.
\twocolwidtha{6cm}
@@ -389,7 +389,7 @@ based on Windows DDE, but available on most platforms using TCP.
\overview{Overview}{docviewoverview}
wxWindows supports a document/view framework which provides
wxWidgets supports a document/view framework which provides
housekeeping for a document-centric application.
\twocolwidtha{6cm}
@@ -449,7 +449,7 @@ facilities.
{\large {\bf File related classes}}
wxWindows has several small classes to work with disk files, see \helpref{file classes
wxWidgets has several small classes to work with disk files, see \helpref{file classes
overview}{wxfileoverview} for more details.
\twocolwidtha{6cm}
@@ -465,7 +465,7 @@ overview}{wxfileoverview} for more details.
{\large {\bf Stream classes}}
wxWindows has its own set of stream classes, as an alternative to often buggy standard stream
wxWidgets has its own set of stream classes, as an alternative to often buggy standard stream
libraries, and to provide enhanced functionality.
\twocolwidtha{6cm}
@@ -500,7 +500,7 @@ libraries, and to provide enhanced functionality.
\overview{Multithreading overview}{wxthreadoverview}
wxWindows provides a set of classes to make use of the native thread
wxWidgets provides a set of classes to make use of the native thread
capabilities of the various platforms.
\twocolwidtha{6cm}
@@ -517,7 +517,7 @@ capabilities of the various platforms.
{\large {\bf HTML classes}}
wxWindows provides a set of classes to display text in HTML format. These
wxWidgets provides a set of classes to display text in HTML format. These
class include a help system based on the HTML widget.
\twocolwidtha{6cm}
@@ -534,7 +534,7 @@ class include a help system based on the HTML widget.
{\large {\bf Virtual file system classes}}
wxWindows provides a set of classes that implement an extensible virtual file system,
wxWidgets provides a set of classes that implement an extensible virtual file system,
used internally by the HTML classes.
\twocolwidtha{6cm}
@@ -575,7 +575,7 @@ from specifications stored in an XML format.
\overview{Database classes overview}{odbcoverview}
wxWindows provides a set of classes for accessing Microsoft's ODBC (Open Database Connectivity)
wxWidgets provides a set of classes for accessing Microsoft's ODBC (Open Database Connectivity)
product, donated by Remstar. This is known as wxODBC.
\twocolwidtha{6cm}

2
docs/latex/wx/checklst.tex
View File

@@ -3,7 +3,7 @@
A checklistbox is like a listbox, but allows items to be checked or unchecked.
This class is currently implemented under Windows and GTK. When using this
class under Windows wxWindows must be compiled with USE\_OWNER\_DRAWN set to 1.
class under Windows wxWidgets must be compiled with USE\_OWNER\_DRAWN set to 1.
Only the new functions for this class are documented; see also \helpref{wxListBox}{wxlistbox}.

2
docs/latex/wx/clasinfo.tex
View File

@@ -68,7 +68,7 @@ Returns the size of the class.
\func{static void}{InitializeClasses}{\void}
Initializes pointers in the wxClassInfo objects for fast execution
of IsKindOf. Called in base wxWindows library initialization.
of IsKindOf. Called in base wxWidgets library initialization.
\membersection{wxClassInfo::IsKindOf}\label{wxclassinfoiskindof}

2
docs/latex/wx/clientdat.tex
View File

@@ -4,7 +4,7 @@ All classes deriving from \helpref{wxEvtHandler}{wxevthandler}
(such as all controls and \helpref{wxApp}{wxapp})
can hold arbitrary data which is here referred to as "client data".
This is useful e.g. for scripting languages which need to handle
shadow objects for most of wxWindows' classes and which store
shadow objects for most of wxWidgets' classes and which store
a handle to such a shadow class as client data in that class.
This data can either be of type void - in which case the data
{\it container} does not take care of freeing the data again

2
docs/latex/wx/clipbrd.tex
View File

@@ -1,7 +1,7 @@
\section{\class{wxClipboard}}\label{wxclipboard}
A class for manipulating the clipboard. Note that this is not compatible with the
clipboard class from wxWindows 1.xx, which has the same name but a different implementation.
clipboard class from wxWidgets 1.xx, which has the same name but a different implementation.
To use the clipboard, you call member functions of the global {\bf wxTheClipboard} object.

4
docs/latex/wx/cmdlpars.tex
View File

@@ -6,7 +6,7 @@
%% Created: 27.03.00
%% RCS-ID: $Id$
%% Copyright: (c) Vadim Zeitlin
%% License: wxWindows license
%% License: wxWidgets license
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\section{\class{wxCmdLineParser}}\label{wxcmdlineparser}
@@ -215,7 +215,7 @@ terminate after this) or a positive number if there was an error during the
command line parsing.
In the latter case, the appropriate error message and usage information are
logged by wxCmdLineParser itself using the standard wxWindows logging functions.
logged by wxCmdLineParser itself using the standard wxWidgets logging functions.
\membersection{Getting results}\label{wxcmdlineparsergettingresults}

6
docs/latex/wx/colour.tex
View File

@@ -261,7 +261,7 @@ Assignment operator for the colour data.
\section{\class{wxColourDatabase}}\label{wxcolourdatabase}
wxWindows maintains a database of standard RGB colours for a predefined
wxWidgets maintains a database of standard RGB colours for a predefined
set of named colours (such as ``BLACK'', ``LIGHT GREY''). The
application may add to this set if desired by using
\helpref{AddColour}{wxcolourdatabaseaddcolour} and may use it to look up
@@ -320,7 +320,7 @@ Adds a colour to the database. If a colour with the same name already exists,
it is replaced.
Please note that the overload taking a pointer is deprecated and will be
removed in the next wxWindows version, please don't use it.
removed in the next wxWidgets version, please don't use it.
\membersection{wxColourDatabase::Find}\label{wxcolourdatabasefind}
@@ -340,7 +340,7 @@ Finds a colour given the name. Returns \tt{NULL} if not found or a pointer which
must be deleted by the caller otherwise.
Please note that this method is deprecated and will be removed in the next
wxWindows version, please use \helpref{Find}{wxcolourdatabasefind} instead of
wxWidgets version, please use \helpref{Find}{wxcolourdatabasefind} instead of
it.

10
docs/latex/wx/config.tex
View File

@@ -9,7 +9,7 @@ you're working with but you would just use the wxConfigBase methods. This
allows you to write the same code regardless of whether you're working with
the registry under Win32 or text-based config files under Unix (or even
Windows 3.1 .INI files if you're really unlucky). To make writing the portable
code even easier, wxWindows provides a typedef wxConfig
code even easier, wxWidgets provides a typedef wxConfig
which is mapped onto the native wxConfigBase implementation on the given
platform: i.e. wxRegConfig under Win32 (optionally wxIniConfig) and
wxFileConfig otherwise.
@@ -26,7 +26,7 @@ No base class
\wxheading{Include files}
<wx/config.h> (to let wxWindows choose a wxConfig class for your platform)\\
<wx/config.h> (to let wxWidgets choose a wxConfig class for your platform)\\
<wx/confbase.h> (base config class)\\
<wx/fileconf.h> (wxFileConfig class)\\
<wx/msw/regconf.h> (wxRegConfig class)\\
@@ -88,14 +88,14 @@ consuming operation). In this case, you may create this global config object
in the very start of the program and {\it Set()} it as the default. Then, from
anywhere in your program, you may access it using the {\it Get()} function.
Note that you must delete this object (usually in \helpref{wxApp::OnExit}{wxapponexit})
in order to avoid memory leaks, wxWindows won't do it automatically.
in order to avoid memory leaks, wxWidgets won't do it automatically.
As it happens, you may even further simplify the procedure described above:
you may forget about calling {\it Set()}. When {\it Get()} is called and there
is no current object, it will create one using {\it Create()} function. To
disable this behaviour {\it DontCreateOnDemand()} is provided.
{\bf Note:} You should use either {\it Set()} or {\it Get()} because wxWindows
{\bf Note:} You should use either {\it Set()} or {\it Get()} because wxWidgets
library itself would take advantage of it and could save various information
in it. For example \helpref{wxFontMapper}{wxfontmapper} or Unix version
of \helpref{wxFileDialog}{wxfiledialog} have ability to use wxConfig class.
@@ -376,7 +376,7 @@ a {\it foo} key with some backslash characters will be stored as {\tt foo=C:$\ba
of the usual storage of {\tt foo=C:$\backslash\backslash$mydir}.
The wxCONFIG\_USE\_NO\_ESCAPE\_CHARACTERS style can be helpful if your config
file must be read or written to by a non-wxWindows program (which might not
file must be read or written to by a non-wxWidgets program (which might not
understand the escape characters). Note, however, that if
wxCONFIG\_USE\_NO\_ESCAPE\_CHARACTERS style is used, it is is now
your application's responsibility to ensure that there is no newline or

2
docs/latex/wx/constant.tex
View File

@@ -2,7 +2,7 @@
\setheader{{\it CHAPTER \thechapter}}{}{}{}{}{{\it CHAPTER \thechapter}}%
\setfooter{\thepage}{}{}{}{}{\thepage}
This chapter describes the constants defined by wxWindows.
This chapter describes the constants defined by wxWidgets.
\input cppconst.tex
\input stdevtid.tex

14
docs/latex/wx/cppconst.tex
View File

@@ -1,13 +1,13 @@
\section{Preprocesser symbols defined by wxWindows}\label{cppconst}
\section{Preprocesser symbols defined by wxWidgets}\label{cppconst}
Here is the list of preprocessor symbols used in the wxWindows source grouped
Here is the list of preprocessor symbols used in the wxWidgets source grouped
by category (and sorted by alphabetical order inside each category).
\subsection{GUI system}
\begin{twocollist}\itemsep=0pt
\twocolitem{\_\_WINDOWS\_\_}{any Windows, yom may also use \_\_WXMSW\_\_}
\twocolitem{\_\_WIN16\_\_}{Win16 API (not supported since wxWindows 2.6)}
\twocolitem{\_\_WIN16\_\_}{Win16 API (not supported since wxWidgets 2.6)}
\twocolitem{\_\_WIN32\_\_}{Win32 API}
\twocolitem{\_\_WIN95\_\_}{Windows 95 or NT 4.0 and above system (not NT 3.5x)}
\twocolitem{\_\_WXBASE\_\_}{Only wxBase, no GUI features}
@@ -26,7 +26,7 @@ defined)}
\twocolitem{\_\_WXPM\_\_}{OS/2 native Presentation Manager}
\twocolitem{\_\_WXSTUBS\_\_}{Stubbed version ('template' wxWin implementation)}
\twocolitem{\_\_WXXT\_\_}{Xt; mutually exclusive with WX\_MOTIF, not
implemented in wxWindows 2.x}
implemented in wxWidgets 2.x}
\twocolitem{\_\_WXX11\_\_}{wxX11 (\_\_WXUNIVERSAL\_\_ will be also defined)}
\twocolitem{\_\_WXWINE\_\_}{WINE (i.e. WIN32 on Unix)}
\twocolitem{\_\_WXUNIVERSAL\_\_}{wxUniversal port, always defined in addition
@@ -105,7 +105,7 @@ the compiler version, $1100$ is $11.0$ and $1200$ is OpenWatcom.}
\subsection{Miscellaneous}
\begin{twocollist}\itemsep=0pt
\twocolitem{\_\_WXWINDOWS\_\_}{always defined in wxWindows applications, see
\twocolitem{\_\_WXWINDOWS\_\_}{always defined in wxWidgets applications, see
also \helpref{wxCHECK\_VERSION}{wxcheckversion}}
\twocolitem{\_\_WXDEBUG\_\_}{defined in debug mode, undefined in release mode}
\twocolitem{wxUSE\_XXX}{if defined as $1$, feature XXX is active
@@ -114,8 +114,8 @@ also \helpref{wxCHECK\_VERSION}{wxcheckversion}}
\twocolitem{wxUSE\_GUI}{this particular feature test macro is defined to $1$
when compiling or using the library with the GUI features activated, if it is
defined as $0$, only wxBase is available.}
\twocolitem{wxUSE\_BASE}{only used by wxWindows internally (defined as $1$ when
\twocolitem{wxUSE\_BASE}{only used by wxWidgets internally (defined as $1$ when
building wxBase code, either as a standalone library or as part of the
monolithic wxWindows library, defined as $0$ when building GUI library only)}
monolithic wxWidgets library, defined as $0$ when building GUI library only)}
\end{twocollist}

6
docs/latex/wx/ctrlsub.tex
View File

@@ -6,12 +6,12 @@
%% Created: 01.01.03
%% RCS-ID: $Id$
%% Copyright: (c) 2003 Vadim Zeitlin
%% License: wxWindows license
%% License: wxWidgets license
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\section{\class{wxControlWithItems}}\label{wxcontrolwithitems}
This class is an abstract base class for some wxWindows controls which contain
This class is an abstract base class for some wxWidgets controls which contain
several items, such as \helpref{wxListBox}{wxlistbox} and
\helpref{wxCheckListBox}{wxchecklistbox} derived from it,
\helpref{wxChoice}{wxchoice} and \helpref{wxComboBox}{wxcombobox}.
@@ -264,7 +264,7 @@ Returns {\tt true} if the control is empty or {\tt false} if it has some items.
{\bf Obsolescence note:} This method is obsolete and was replaced with
\helpref{GetCount}{wxcontrolwithitemsgetcount}, please use the new method in
the new code. This method is only available if wxWindows was compiled with
the new code. This method is only available if wxWidgets was compiled with
{\tt WXWIN\_COMPATIBILITY\_2\_2} defined and will disappear completely in
future versions.

4
docs/latex/wx/cursor.tex
View File

@@ -10,7 +10,7 @@ conditional compilation will probably be required (see \helpref{wxIcon}{wxicon}
an example).
A single cursor object may be used in many windows (any subwindow type).
The wxWindows convention is to set the cursor for a window, as in X,
The wxWidgets convention is to set the cursor for a window, as in X,
rather than to set it globally as in MS Windows, although a
global \helpref{::wxSetCursor}{wxsetcursor} is also available for MS Windows use.
@@ -231,7 +231,7 @@ wxCursor down_cursor = wxCursor(down_bits, 32, 32,
Destroys the cursor. A cursor can be reused for more
than one window, and does not get destroyed when the window is
destroyed. wxWindows destroys all cursors on application exit, although
destroyed. wxWidgets destroys all cursors on application exit, although
it is best to clean them up explicitly.
\membersection{wxCursor::Ok}\label{wxcursorok}

2
docs/latex/wx/dataform.tex
View File

@@ -6,7 +6,7 @@
%% Created: 03.11.99
%% RCS-ID: $Id$
%% Copyright: (c) Vadim Zeitlin
%% License: wxWindows license
%% License: wxWidgets license
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\section{\class{wxDataFormat}}\label{wxdataformat}

6
docs/latex/wx/dataobj.tex
View File

@@ -5,8 +5,8 @@
%% Modified by:
%% Created: 18.10.99
%% RCS-ID: $Id$
%% Copyright: (c) wxWindows team
%% License: wxWindows license
%% Copyright: (c) wxWidgets team
%% License: wxWidgets license
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\section{\class{wxDataObject}}\label{wxdataobject}
@@ -41,7 +41,7 @@ reasonable for the situations when you really need to support multiple formats,
but may be annoying if you only want to do something simple like cut and paste
text.
To provide a solution for both cases, wxWindows has two predefined classes
To provide a solution for both cases, wxWidgets has two predefined classes
which derive from wxDataObject: \helpref{wxDataObjectSimple}{wxdataobjectsimple} and
\helpref{wxDataObjectComposite}{wxdataobjectcomposite}.
\helpref{wxDataObjectSimple}{wxdataobjectsimple} is

2
docs/latex/wx/datespan.tex
View File

@@ -6,7 +6,7 @@
%% Created: 04.04.00
%% RCS-ID: $Id$
%% Copyright: (c) Vadim Zeitlin
%% License: wxWindows license
%% License: wxWidgets license
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\section{\class{wxDateSpan}}\label{wxdatespan}

4
docs/latex/wx/datetime.tex
View File

@@ -6,7 +6,7 @@
%% Created: 07.03.00
%% RCS-ID: $Id$
%% Copyright: (c) Vadim Zeitlin
%% License: wxWindows license
%% License: wxWidgets license
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\section{\class{wxDateTime}}\label{wxdatetime}
@@ -1112,7 +1112,7 @@ the character which stopped the scan.
This function does the same as the standard ANSI C {\tt strftime(3)} function.
Please see its description for the meaning of {\it format} parameter.
It also accepts a few wxWindows-specific extensions: you can optionally specify
It also accepts a few wxWidgets-specific extensions: you can optionally specify
the width of the field to follow using {\tt printf(3)}-like syntax and the
format specification {\tt \%l} can be used to get the number of milliseconds.

4
docs/latex/wx/datistrm.tex
View File

@@ -46,7 +46,7 @@ None
\func{}{wxDataInputStream}{\param{wxInputStream\&}{ stream}, \param{wxMBConv\&}{ conv = wxMBConvUTF8}}
Constructs a datastream object from an input stream. Only read methods will
be available. The second form is only available in Unicode build of wxWindows.
be available. The second form is only available in Unicode build of wxWidgets.
\wxheading{Parameters}
@@ -135,7 +135,7 @@ Reads a string from a stream. Actually, this function first reads a long
integer specifying the length of the string (without the last null character)
and then reads the string.
In Unicode build of wxWindows, the fuction first reads multibyte (char*)
In Unicode build of wxWidgets, the fuction first reads multibyte (char*)
string from the stream and then converts it to Unicode using the {\it conv}
object passed to constructor and returns the result as wxString. You are
responsible for using the same convertor as when writing the stream.

4
docs/latex/wx/datostrm.tex
View File

@@ -26,7 +26,7 @@ None
\func{}{wxDataOutputStream}{\param{wxOutputStream\&}{ stream}, \param{wxMBConv\&}{ conv = wxMBConvUTF8}}
Constructs a datastream object from an output stream. Only write methods will
be available. The second form is only available in Unicode build of wxWindows.
be available. The second form is only available in Unicode build of wxWidgets.
\wxheading{Parameters}
@@ -116,7 +116,7 @@ specified with the {\it size} variable.
Writes {\it string} to the stream. Actually, this method writes the size of
the string before writing {\it string} itself.
In ANSI build of wxWindows, the string is written to the stream in exactly
In ANSI build of wxWidgets, the string is written to the stream in exactly
same way it is represented in memory. In Unicode build, however, the string
is first converted to multibyte representation with {\it conv} object passed
to stream's constructor (consequently, ANSI application can read data

16
docs/latex/wx/db.tex
View File

@@ -254,7 +254,7 @@ ODBC errors.}
\wxheading{Remarks}
Default cursor scrolling is defined by wxODBC\_FWD\_ONLY\_CURSORS in setup.h
when the wxWindows library is built. This behavior can be overridden when
when the wxWidgets library is built. This behavior can be overridden when
an instance of a wxDb is created (see \helpref{wxDb constructor}{wxdbconstr}).
Default setting of this value true, as not all databases/drivers support
both types of cursors.
@@ -596,7 +596,7 @@ Possible values returned by this function can be viewed in the
\helpref{Enumerated types}{wxdbenumeratedtypes} section of wxDb.
There are known issues with conformance to the ODBC standards with several
datasources supported by the wxWindows ODBC classes. Please see the overview
datasources supported by the wxWidgets ODBC classes. Please see the overview
for specific details on which datasource have which issues.
\wxheading{Return value}
@@ -731,7 +731,7 @@ of processing.
\func{bool}{IsFwdOnlyCursors}{\void}
Older form (pre-2.3/2.4 of wxWindows) of the
Older form (pre-2.3/2.4 of wxWidgets) of the
\helpref{wxDb::IsFwdOnlyCursors}{wxdbisfwdonlycursors}. This method is
provided for backward compatibility only. The method
\helpref{wxDb::IsFwdOnlyCursors}{wxdbisfwdonlycursors} should be
@@ -1093,12 +1093,12 @@ use backward scrolling cursors and their associated functions (see note above).
\wxheading{Remarks}
Added as of wxWindows v2.4 release, this function is a renamed version of
wxDb::FwdOnlyCursors() to match the normal wxWindows naming conventions for
Added as of wxWidgets v2.4 release, this function is a renamed version of
wxDb::FwdOnlyCursors() to match the normal wxWidgets naming conventions for
class member functions.
This function is not available in versions prior to v2.4. You should
use \helpref{wxDb::FwdOnlyCursors}{wxdbfwdonlycursors} for wxWindows
use \helpref{wxDb::FwdOnlyCursors}{wxdbfwdonlycursors} for wxWidgets
versions prior to 2.4.
\wxheading{See also}
@@ -1963,7 +1963,7 @@ class so a program can create a wxDbTableInf array instance to maintain all
information about all tables in the datasource to have all the datasource's
information in one memory structure.
Primarily, this class is used internally by the wxWindows ODBC classes.
Primarily, this class is used internally by the wxWidgets ODBC classes.
\begin{verbatim}
wxChar catalog[128+1];
@@ -3054,7 +3054,7 @@ calls which defined the columns accessible to this wxDbTable instance.}
\wxheading{Remarks}
NULL column support is currently not fully implemented as of wxWindows 2.4.
NULL column support is currently not fully implemented as of wxWidgets 2.4.
\membersection{wxDbTable::IsCursorClosedOnCommit}\label{wxdbtableiscursorclosedoncommit}

8
docs/latex/wx/dc.tex
View File

@@ -109,7 +109,7 @@ This sequence of operations ensures that the source's transparent area need not
and logical functions are supported.
{\bf Note:} on Windows, blitting with masks can be speeded up considerably by compiling
wxWindows with the wxUSE\_DC\_CACHE option enabled. You can also influence whether MaskBlt
wxWidgets with the wxUSE\_DC\_CACHE option enabled. You can also influence whether MaskBlt
or the explicit mask blitting code above is used, by using \helpref{wxSystemOptions}{wxsystemoptions} and
setting the {\bf no-maskblt} option to 1.
@@ -383,7 +383,7 @@ The current pen is used for drawing the outline, and the current brush
for filling the shape. Using a transparent brush suppresses filling.
The programmer is responsible for deleting the list of points.
Note that wxWindows automatically closes the first and last points.
Note that wxWidgets automatically closes the first and last points.
\pythonnote{The wxPython version of this method accepts a Python list
of wxPoint objects.}
@@ -1071,9 +1071,9 @@ The mapping mode can be one of the following:
If {\it optimize} is true (the default), this function sets optimization mode on.
This currently means that under X, the device context will not try to set a pen or brush
property if it is known to be set already. This approach can fall down
if non-wxWindows code is using the same device context or window, for example
if non-wxWidgets code is using the same device context or window, for example
when the window is a panel on which the windowing system draws panel items.
The wxWindows device context 'memory' will now be out of step with reality.
The wxWidgets device context 'memory' will now be out of step with reality.
Setting optimization off, drawing, then setting it back on again, is a trick
that must occasionally be employed.

2
docs/latex/wx/debugcxt.tex
View File

@@ -2,7 +2,7 @@
A class for performing various debugging and memory tracing
operations. Full functionality (such as printing out objects
currently allocated) is only present in a debugging build of wxWindows,
currently allocated) is only present in a debugging build of wxWidgets,
i.e. if the \_\_WXDEBUG\_\_ symbol is defined. wxDebugContext
and related functions and macros can be compiled out by setting
wxUSE\_DEBUG\_CONTEXT to 0 is setup.h

2
docs/latex/wx/delgrend.tex
View File

@@ -6,7 +6,7 @@
%% Created: 11.08.03
%% RCS-ID: $Id$
%% Copyright: (c) 2003 Vadim Zeitlin <vadim@wxwindows.org>
%% License: wxWindows license
%% License: wxWidgets license
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\section{\class{wxDelegateRendererNative}}\label{wxdelegaterenderernative}

2
docs/latex/wx/dialevt.tex
View File

@@ -6,7 +6,7 @@
%% Created: 08.04.00
%% RCS-ID: $Id$
%% Copyright: (c) Vadim Zeitlin
%% License: wxWindows license
%% License: wxWidgets license
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\section{\class{wxDialUpEvent}}\label{wxdialupevent}

6
docs/latex/wx/dialog.tex
View File

@@ -77,7 +77,7 @@ with a {\tt NULL} parent window will be given the
\helpref{application's top level window}{wxappgettopwindow} as parent. Use this
style to prevent this from happening and create an orphan dialog. This is not recommended for modal dialogs.}
\twocolitem{\windowstyle{wxDIALOG\_EX\_CONTEXTHELP}}{Under Windows, puts a query button on the
caption. When pressed, Windows will go into a context-sensitive help mode and wxWindows will send
caption. When pressed, Windows will go into a context-sensitive help mode and wxWidgets will send
a wxEVT\_HELP event if the user clicked on an application window. {\it Note}\ that this is an extended
style and must be set by calling \helpref{SetExtraStyle}{wxwindowsetextrastyle} before Create is called (two-step construction).}
\end{twocollist}
@@ -119,10 +119,10 @@ Constructor.
\docparam{title}{The title of the dialog.}
\docparam{pos}{The dialog position. A value of (-1, -1) indicates a default position, chosen by
either the windowing system or wxWindows, depending on platform.}
either the windowing system or wxWidgets, depending on platform.}
\docparam{size}{The dialog size. A value of (-1, -1) indicates a default size, chosen by
either the windowing system or wxWindows, depending on platform.}
either the windowing system or wxWidgets, depending on platform.}
\docparam{style}{The window style. See \helpref{wxDialog}{wxdialog}.}

4
docs/latex/wx/dialup.tex
View File

@@ -6,7 +6,7 @@
%% Created: 08.04.00
%% RCS-ID: $Id$
%% Copyright: (c) Vadim Zeitlin
%% License: wxWindows license
%% License: wxWidgets license
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\section{\class{wxDialUpManager}}\label{wxdialupmanager}
@@ -22,7 +22,7 @@ network the next time or, on the contrary, to stop receiving data from the net
when the user hangs up the modem). For this, you need to use one of the event
macros described below.
This class is different from other wxWindows classes in that there is at most
This class is different from other wxWidgets classes in that there is at most
one instance of this class in the program accessed via
\helpref{wxDialUpManager::Create()}{wxdialupmanagercreate} and you can't
create the objects of this class directly.

2
docs/latex/wx/dir.tex
View File

@@ -6,7 +6,7 @@
%% Created: 04.04.00
%% RCS-ID: $Id$
%% Copyright: (c) Vadim Zeitlin
%% License: wxWindows license
%% License: wxWidgets license
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\section{\class{wxDir}}\label{wxdir}

2
docs/latex/wx/dirtrav.tex
View File

@@ -6,7 +6,7 @@
%% Created: 14.01.02 (extracted from dir.tex)
%% RCS-ID: $Id$
%% Copyright: (c) Vadim Zeitlin
%% License: wxWindows license
%% License: wxWidgets license
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\section{\class{wxDirTraverser}}\label{wxdirtraverser}

2
docs/latex/wx/dllload.tex
View File

@@ -6,7 +6,7 @@
%% Created: 02.04.00
%% RCS-ID: $Id$
%% Copyright: (c) Vadim Zeitlin
%% License: wxWindows license
%% License: wxWidgets license
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\section{\class{wxDllLoader}}\label{wxdllloader}

2
docs/latex/wx/dobjcomp.tex
View File

@@ -6,7 +6,7 @@
%% Created: 02.11.99
%% RCS-ID: $Id$
%% Copyright: (c) Vadim Zeitlin
%% License: wxWindows license
%% License: wxWidgets license
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\section{\class{wxDataObjectComposite}}\label{wxdataobjectcomposite}

2
docs/latex/wx/dobjsmpl.tex
View File

@@ -6,7 +6,7 @@
%% Created: 02.11.99
%% RCS-ID: $Id$
%% Copyright: (c) Vadim Zeitlin
%% License: wxWindows license
%% License: wxWidgets license
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\section{\class{wxDataObjectSimple}}\label{wxdataobjectsimple}

2
docs/latex/wx/docchfrm.tex
View File

@@ -3,7 +3,7 @@
The wxDocChildFrame class provides a default frame for displaying documents
on separate windows. This class can only be used for SDI (not MDI) child frames.
The class is part of the document/view framework supported by wxWindows,
The class is part of the document/view framework supported by wxWidgets,
and cooperates with the \helpref{wxView}{wxview}, \helpref{wxDocument}{wxdocument},
\rtfsp\helpref{wxDocManager}{wxdocmanager} and \helpref{wxDocTemplate}{wxdoctemplate} classes.

2
docs/latex/wx/docmanag.tex
View File

@@ -1,6 +1,6 @@
\section{\class{wxDocManager}}\label{wxdocmanager}
The wxDocManager class is part of the document/view framework supported by wxWindows,
The wxDocManager class is part of the document/view framework supported by wxWidgets,
and cooperates with the \helpref{wxView}{wxview}, \helpref{wxDocument}{wxdocument}\rtfsp
and \helpref{wxDocTemplate}{wxdoctemplate} classes.

2
docs/latex/wx/docmdich.tex
View File

@@ -3,7 +3,7 @@
The wxDocMDIChildFrame class provides a default frame for displaying documents
on separate windows. This class can only be used for MDI child frames.
The class is part of the document/view framework supported by wxWindows,
The class is part of the document/view framework supported by wxWidgets,
and cooperates with the \helpref{wxView}{wxview}, \helpref{wxDocument}{wxdocument},
\rtfsp\helpref{wxDocManager}{wxdocmanager} and \helpref{wxDocTemplate}{wxdoctemplate} classes.

6
docs/latex/wx/document.tex
View File

@@ -1,7 +1,7 @@
\section{\class{wxDocument}}\label{wxdocument}
The document class can be used to model an application's file-based
data. It is part of the document/view framework supported by wxWindows,
data. It is part of the document/view framework supported by wxWidgets,
and cooperates with the \helpref{wxView}{wxview}, \helpref{wxDocTemplate}{wxdoctemplate}\rtfsp
and \helpref{wxDocManager}{wxdocmanager} classes.
@@ -200,7 +200,7 @@ Override this function and call it from your own LoadObject before
streaming your own data. LoadObject is called by the framework
automatically when the document contents need to be loaded.
Note that only one of these forms exists, depending on how wxWindows
Note that only one of these forms exists, depending on how wxWidgets
was configured.
\membersection{wxDocument::Modify}\label{wxdocumentmodify}
@@ -311,7 +311,7 @@ Override this function and call it from your own SaveObject before
streaming your own data. SaveObject is called by the framework
automatically when the document contents need to be saved.
Note that only one of these forms exists, depending on how wxWindows
Note that only one of these forms exists, depending on how wxWidgets
was configured.
\membersection{wxDocument::SetCommandProcessor}

4
docs/latex/wx/dynlib.tex
View File

@@ -6,7 +6,7 @@
%% Created: 14.01.02 (extracted from dllload.tex)
%% RCS-ID: $Id$
%% Copyright: (c) Vadim Zeitlin
%% License: wxWindows license
%% License: wxWidgets license
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\section{\class{wxDynamicLibrary}}\label{wxdynamiclibrary}
@@ -56,7 +56,7 @@ The possible values for \arg{cat} are:
\func{wxString}{CanonicalizePluginName}{\param{const wxString\& }{name}, \param{wxPluginCategory}{ cat = wxDL\_PLUGIN\_GUI}}
This function does the same thing as
\helpref{CanonicalizeName}{wxdynamiclibrarycanonicalizename} but for wxWindows
\helpref{CanonicalizeName}{wxdynamiclibrarycanonicalizename} but for wxWidgets
plugins. The only difference is that compiler and version information are added
to the name to ensure that the plugin which is going to be loaded will be
compatible with the main program.

6
docs/latex/wx/encconv.tex
View File

@@ -7,7 +7,7 @@
This class is capable of converting strings between two
8-bit encodings/charsets. It can also convert from/to Unicode (but only
if you compiled wxWindows with wxUSE\_WCHAR\_T set to 1). Only limited subset
if you compiled wxWidgets with wxUSE\_WCHAR\_T set to 1). Only limited subset
of encodings in supported by wxEncodingConverter:
{\tt wxFONTENCODING\_ISO8859\_1..15}, {\tt wxFONTENCODING\_CP1250..1257} and
{\tt wxFONTENCODING\_KOI8}.
@@ -76,7 +76,7 @@ as input string.
false if given conversion is impossible, true otherwise
(conversion may be impossible either if you try to convert
to Unicode with non-Unicode build of wxWindows or if input
to Unicode with non-Unicode build of wxWidgets or if input
or output encoding is not supported.)
@@ -121,7 +121,7 @@ Convert wxString and return new wxString object.
You must call \helpref{Init}{wxencodingconverterinit} before using this method!
{\tt wchar\_t} versions of the method are not available if wxWindows was compiled
{\tt wchar\_t} versions of the method are not available if wxWidgets was compiled
with {\tt wxUSE\_WCHAR\_T} set to 0.

6
docs/latex/wx/event.tex
View File

@@ -84,14 +84,14 @@ Timestamp for this event.
Returns a copy of the event.
Any event that is posted to the wxWindows event system for later action (via
Any event that is posted to the wxWidgets event system for later action (via
\helpref{wxEvtHandler::AddPendingEvent}{wxevthandleraddpendingevent} or
\helpref{wxPostEvent}{wxpostevent}) must implement this method. All wxWindows
\helpref{wxPostEvent}{wxpostevent}) must implement this method. All wxWidgets
events fully implement this method, but any derived events implemented by the
user should also implement this method just in case they (or some event
derived from them) are ever posted.
All wxWindows events implement a copy constructor, so the easiest way of
All wxWidgets events implement a copy constructor, so the easiest way of
implementing the Clone function is to implement a copy constructor for
a new event (call it MyEvent) and then define the Clone function like this:

4
docs/latex/wx/evthand.tex
View File

@@ -226,14 +226,14 @@ call \helpref{wxEvent::Skip}{wxeventskip}.
\wxheading{Remarks}
Normally, your application would not call this function: it is called in the wxWindows
Normally, your application would not call this function: it is called in the wxWidgets
implementation to dispatch incoming user interface events to the framework (and application).
However, you might need to call it if implementing new functionality (such as a new control) where
you define new event types, as opposed to allowing the user to override virtual functions.
An instance where you might actually override the {\bf ProcessEvent} function is where you want
to direct event processing to event handlers not normally noticed by wxWindows. For example,
to direct event processing to event handlers not normally noticed by wxWidgets. For example,
in the document/view architecture, documents and views are potential event handlers.
When an event reaches a frame, {\bf ProcessEvent} will need to be called on the associated
document and view in case event handler functions are associated with these objects.

4
docs/latex/wx/fdrepdlg.tex
View File

@@ -6,7 +6,7 @@
%% Created: 01.08.01
%% RCS-ID: $Id$
%% Copyright: (c) 2001 Vadim Zeitlin
%% License: wxWindows license
%% License: wxWidgets license
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\section{\class{wxFindDialogEvent}}\label{wxfinddialogevent}
@@ -46,7 +46,7 @@ any pointers to it cannot be used any longer.}
\func{}{wxFindDialogEvent}{\param{wxEventType }{commandType = wxEVT\_NULL}, \param{int }{id = 0}}
Constuctor used by wxWindows only.
Constuctor used by wxWidgets only.
\membersection{wxFindDialogEvent::GetFlags}\label{wxfinddialogeventgetflags}

4
docs/latex/wx/ffile.tex
View File

@@ -6,7 +6,7 @@
%% Created: 14.01.02 (extracted from file.tex)
%% RCS-ID: $Id$
%% Copyright: (c) Vadim Zeitlin
%% License: wxWindows license
%% License: wxWidgets license
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\section{\class{wxFFile}}\label{wxffile}
@@ -245,7 +245,7 @@ Number of bytes written.
Writes the contents of the string to the file, returns \true on success.
The second argument is only meaningful in Unicode build of wxWindows when
The second argument is only meaningful in Unicode build of wxWidgets when
{\it conv} is used to convert {\it s} to multibyte representation.

2
docs/latex/wx/fildatob.tex
View File

@@ -9,7 +9,7 @@ class.
{\bf Warning:} Under all non-Windows platforms this class is currently
"input-only", i.e. you can receive the files from another application, but
copying (or dragging) file(s) from a wxWindows application is not currently
copying (or dragging) file(s) from a wxWidgets application is not currently
supported.
\wxheading{Virtual functions to override}

4
docs/latex/wx/file.tex
View File

@@ -6,7 +6,7 @@
%% Created: 14.01.02 (extracted from file.tex)
%% RCS-ID: $Id$
%% Copyright: (c) Vadim Zeitlin
%% License: wxWindows license
%% License: wxWidgets license
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\section{\class{wxFile}}\label{wxfile}
@@ -295,7 +295,7 @@ the number of bytes actually written
Writes the contents of the string to the file, returns true on success.
The second argument is only meaningful in Unicode build of wxWindows when
The second argument is only meaningful in Unicode build of wxWidgets when
{\it conv} is used to convert {\it s} to multibyte representation.
Note that this method only works with {\tt NUL}-terminated strings, if you want

2
docs/latex/wx/filedlg.tex
View File

@@ -85,7 +85,7 @@ wildcards; see the Remarks section above.}
\docparam{pos}{Dialog position. Not implemented.}
{\bf NB:} Previous versions of wxWindows used {\tt wxCHANGE\_DIR} by default
{\bf NB:} Previous versions of wxWidgets used {\tt wxCHANGE\_DIR} by default
under MS Windows which allowed the program to simply remember the last
directory where user selected the files to open/save. This (desired)
functionality must be implemented in the program itself now (manually remember

4
docs/latex/wx/filename.tex
View File

@@ -6,7 +6,7 @@
%% Created: 30.11.01
%% RCS-ID: $Id$
%% Copyright: (c) 2001 Vadim Zeitlin
%% License: wxWindows license
%% License: wxWidgets license
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\section{\class{wxFileName}}\label{wxfilename}
@@ -14,7 +14,7 @@
wxFileName encapsulates a file name. This class serves two purposes: first, it
provides the functions to split the file names into components and to recombine
these components in the full file name which can then be passed to the OS file
functions (and \helpref{wxWindows functions}{filefunctions} wrapping them).
functions (and \helpref{wxWidgets functions}{filefunctions} wrapping them).
Second, it includes the functions for working with the files itself. Note that
to change the file data you should use \helpref{wxFile}{wxfile} class instead.
wxFileName provides functions for working with the file attributes.

2
docs/latex/wx/flexsizr.tex
View File

@@ -6,7 +6,7 @@ height and all fields in one column having the same width, but all
rows or all columns are not necessarily the same height or width as in
the \helpref{wxGridSizer}{wxgridsizer}.
Since wxWindows 2.5.0, wxFlexGridSizer can also size items equally in one
Since wxWidgets 2.5.0, wxFlexGridSizer can also size items equally in one
direction but unequally ("flexibly") in the other. If the sizer is only
flexible in one direction (this can be changed using
\helpref{SetFlexibleDrection}{wxflexgridsizersetflexibledirection}),

4
docs/latex/wx/font.tex
View File

@@ -203,7 +203,7 @@ system, since wxFont uses a reference counting system for efficiency.
Although all remaining fonts are deleted when the application exits,
the application should try to clean up all fonts itself. This is because
wxWindows cannot know if a pointer to the font object is stored in an
wxWidgets cannot know if a pointer to the font object is stored in an
application data structure, and there is a risk of double deletion.
\membersection{wxFont::IsFixedWidth}\label{wxfontisfixedwidth}
@@ -330,7 +330,7 @@ Sets the facename for the font.
To avoid portability problems, don't rely on a specific face, but specify the font family
instead or as well. A suitable font will be found on the end-user's system. If both the
family and the facename are specified, wxWindows will first search for the specific face,
family and the facename are specified, wxWidgets will first search for the specific face,
and then for a font belonging to the same family.
\wxheading{See also}

2
docs/latex/wx/fontenum.tex
View File

@@ -6,7 +6,7 @@
%% Created: 03.11.99
%% RCS-ID: $Id$
%% Copyright: (c) Vadim Zeitlin
%% License: wxWindows license
%% License: wxWidgets license
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\section{\class{wxFontEnumerator}}\label{wxfontenumerator}

4
docs/latex/wx/fontlist.tex
View File

@@ -33,7 +33,7 @@ use the object pointer {\bf wxTheFontList}.
\func{void}{AddFont}{\param{wxFont *}{font}}
Used by wxWindows to add a font to the list, called in the font constructor.
Used by wxWidgets to add a font to the list, called in the font constructor.
\membersection{wxFontList::FindOrCreateFont}\label{findorcreatefont}
@@ -47,6 +47,6 @@ details of the arguments.
\func{void}{RemoveFont}{\param{wxFont *}{font}}
Used by wxWindows to remove a font from the list.
Used by wxWidgets to remove a font from the list.

4
docs/latex/wx/fontmap.tex
View File

@@ -125,7 +125,7 @@ available on this system). If successful, return true and fill info
structure with the parameters required to create the font, otherwise
return false.
The first form is for wxWindows' internal use while the second one
The first form is for wxWidgets' internal use while the second one
is better suitable for general use -- it returns wxFontEncoding which
can consequently be passed to wxFont constructor.
@@ -208,7 +208,7 @@ The title for the dialogs (note that default is quite reasonable).
Set the current font mapper object and return previous one (may be NULL).
This method is only useful if you want to plug-in an alternative font mapper
into wxWindows.
into wxWidgets.
\wxheading{See also}

16
docs/latex/wx/frame.tex
View File

@@ -47,7 +47,7 @@ Has no effect under other platforms.}
on top of its parent (unlike wxSTAY\_ON\_TOP). A frame created with this style
must have a non-NULL parent.}
\twocolitem{\windowstyle{wxFRAME\_EX\_CONTEXTHELP}}{Under Windows, puts a query button on the
caption. When pressed, Windows will go into a context-sensitive help mode and wxWindows will send
caption. When pressed, Windows will go into a context-sensitive help mode and wxWidgets will send
a wxEVT\_HELP event if the user clicked on an application window. {\it Note} that this is an extended
style and must be set by calling \helpref{SetExtraStyle}{wxwindowsetextrastyle} before Create is called (two-step construction).
You cannot use this style together with wxMAXIMIZE\_BOX or wxMINIMIZE\_BOX, so
@@ -117,10 +117,10 @@ always be displayed on top of the parent window on Windows.}
\docparam{title}{The caption to be displayed on the frame's title bar.}
\docparam{pos}{The window position. A value of (-1, -1) indicates a default position, chosen by
either the windowing system or wxWindows, depending on platform.}
either the windowing system or wxWidgets, depending on platform.}
\docparam{size}{The window size. A value of (-1, -1) indicates a default size, chosen by
either the windowing system or wxWindows, depending on platform.}
either the windowing system or wxWidgets, depending on platform.}
\docparam{style}{The window style. See \helpref{wxFrame}{wxframe}.}
@@ -190,7 +190,7 @@ value greater than 1 to create a multi-field status bar.}
of valid styles.}
\docparam{id}{The status bar window identifier. If -1, an identifier will be chosen by
wxWindows.}
wxWidgets.}
\docparam{name}{The status bar window name.}
@@ -227,7 +227,7 @@ Creates a toolbar at the top or left of the frame.
of valid styles.}
\docparam{id}{The toolbar window identifier. If -1, an identifier will be chosen by
wxWindows.}
wxWidgets.}
\docparam{name}{The toolbar window name.}
@@ -377,7 +377,7 @@ Virtual function called when a status bar is requested by \helpref{wxFrame::Crea
of valid styles.}
\docparam{id}{The window identifier. If -1, an identifier will be chosen by
wxWindows.}
wxWidgets.}
\docparam{name}{The window name.}
@@ -407,7 +407,7 @@ Virtual function called when a toolbar is requested by \helpref{wxFrame::CreateT
of valid styles.}
\docparam{id}{The toolbar window identifier. If -1, an identifier will be chosen by
wxWindows.}
wxWidgets.}
\docparam{name}{The toolbar window name.}
@@ -492,7 +492,7 @@ See also \helpref{wxIconBundle}{wxiconbundle}.
%\end{verbatim}
%
%You can replace std.ico, mdi.ico and child.ico with your own defaults
%for all your wxWindows application. Currently they show the same icon.
%for all your wxWidgets application. Currently they show the same icon.
\membersection{wxFrame::SetMenuBar}\label{wxframesetmenubar}

4
docs/latex/wx/fs.tex
View File

@@ -31,7 +31,7 @@ Locations (aka filenames aka addresses) are constructed from four parts:
\item {\bf protocol} - handler can recognize if it is able to open a
file by checking its protocol. Examples are "http", "file" or "ftp".
\item {\bf right location} - is the name of file within the protocol.
In "http://www.wxwindows.org/index.html" the right location is "//www.wxwindows.org/index.html".
In "http://www.wxwidgets.org/index.html" the right location is "//www.wxwidgets.org/index.html".
\item {\bf anchor} - an anchor is optional and is usually not present.
In "index.htm\#chapter2" the anchor is "chapter2".
\item {\bf left location} - this is usually an empty string.
@@ -55,7 +55,7 @@ There are {\bf two} protocols used in this example: "zip" and "file".
\wxheading{File Systems Included in wxHTML}
The following virtual file system handlers are part of wxWindows so far:
The following virtual file system handlers are part of wxWidgets so far:
\begin{twocollist}
\twocolitem{{\bf wxInternetFSHandler}}{A handler for accessing documents

2
docs/latex/wx/fs_mem.tex
View File

@@ -87,7 +87,7 @@ data (bitmap, text or raw data)
will be copied into private memory stream and available under
name "memory:" + filename.
Note that when storing image/bitmap, you must use image format that wxWindows
Note that when storing image/bitmap, you must use image format that wxWidgets
can write (e.g. JPG, PNG, see \helpref{wxImage documentation}{wximage})!

2
docs/latex/wx/fsfile.tex
View File

@@ -98,7 +98,7 @@ Returns full location of the file, including path and protocol.
Examples :
\begin{verbatim}
http://www.wxwindows.org
http://www.wxwidgets.org
http://www.ms.mff.cuni.cz/~vsla8348/wxhtml/archive.zip#zip:info.txt
file:/home/vasek/index.htm
relative-file.htm

6
docs/latex/wx/ftp.tex
View File

@@ -5,8 +5,8 @@
%% Modified by:
%% Created: ~1997
%% RCS-ID: $Id$
%% Copyright: (c) wxWindows team
%% License: wxWindows license
%% Copyright: (c) wxWidgets team
%% License: wxWidgets license
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\section{\class{wxFTP}}\label{wxftp}
@@ -37,7 +37,7 @@ Example of using wxFTP for file downloading:
}
ftp.ChDir("/pub");
wxInputStream *in = ftp.GetInputStream("wxWindows-4.2.0.tar.gz");
wxInputStream *in = ftp.GetInputStream("wxWidgets-4.2.0.tar.gz");
if ( !in )
{
wxLogError("Coudln't get file");

78
docs/latex/wx/function.tex
View File

@@ -2,7 +2,7 @@
\setheader{{\it CHAPTER \thechapter}}{}{}{}{}{{\it CHAPTER \thechapter}}%
\setfooter{\thepage}{}{}{}{}{\thepage}
The functions and macros defined in wxWindows are described here: you can
The functions and macros defined in wxWidgets are described here: you can
either look up a function using the alphabetical listing of them or find it in
the corresponding topic.
@@ -244,21 +244,21 @@ the corresponding topic.
\section{Version macros}\label{versionfunctions}
The following constants are defined in wxWindows:
The following constants are defined in wxWidgets:
\begin{itemize}\itemsep=0pt
\item {\tt wxMAJOR\_VERSION} is the major version of wxWindows
\item {\tt wxMINOR\_VERSION} is the minor version of wxWindows
\item {\tt wxMAJOR\_VERSION} is the major version of wxWidgets
\item {\tt wxMINOR\_VERSION} is the minor version of wxWidgets
\item {\tt wxRELEASE\_NUMBER} is the release number
\end{itemize}
For example, the values or these constants for wxWindows 2.1.15 are 2, 1 and
For example, the values or these constants for wxWidgets 2.1.15 are 2, 1 and
15.
Additionally, {\tt wxVERSION\_STRING} is a user-readable string containing
the full wxWindows version and {\tt wxVERSION\_NUMBER} is a combination of the
the full wxWidgets version and {\tt wxVERSION\_NUMBER} is a combination of the
three version numbers above: for 2.1.15, it is 2115 and it is 2200 for
wxWindows 2.2.
wxWidgets 2.2.
\wxheading{Include files}
@@ -269,10 +269,10 @@ wxWindows 2.2.
\func{bool}{wxCHECK\_VERSION}{\param{}{major, minor, release}}
This is a macro which evaluates to true if the current wxWindows version is at
This is a macro which evaluates to true if the current wxWidgets version is at
least major.minor.release.
For example, to test if the program is compiled with wxWindows 2.2 or higher,
For example, to test if the program is compiled with wxWidgets 2.2 or higher,
the following can be done:
\begin{verbatim}
@@ -315,31 +315,31 @@ to control the behaviour of the main event loop of the GUI programs.
\membersection{::wxEntry}\label{wxentry}
This initializes wxWindows in a platform-dependent way. Use this if you
are not using the default wxWindows entry code (e.g. main or WinMain). For example,
you can initialize wxWindows from an Microsoft Foundation Classes application using
This initializes wxWidgets in a platform-dependent way. Use this if you
are not using the default wxWidgets entry code (e.g. main or WinMain). For example,
you can initialize wxWidgets from an Microsoft Foundation Classes application using
this function.
\func{void}{wxEntry}{\param{HANDLE}{ hInstance}, \param{HANDLE}{ hPrevInstance},
\param{const wxString\& }{commandLine}, \param{int}{ cmdShow}, \param{bool}{ enterLoop = true}}
wxWindows initialization under Windows (non-DLL). If {\it enterLoop} is false, the
function will return immediately after calling wxApp::OnInit. Otherwise, the wxWindows
wxWidgets initialization under Windows (non-DLL). If {\it enterLoop} is false, the
function will return immediately after calling wxApp::OnInit. Otherwise, the wxWidgets
message loop will be entered.
\func{void}{wxEntry}{\param{HANDLE}{ hInstance}, \param{HANDLE}{ hPrevInstance},
\param{WORD}{ wDataSegment}, \param{WORD}{ wHeapSize}, \param{const wxString\& }{ commandLine}}
wxWindows initialization under Windows (for applications constructed as a DLL).
wxWidgets initialization under Windows (for applications constructed as a DLL).
\func{int}{wxEntry}{\param{int}{ argc}, \param{const wxString\& *}{argv}}
wxWindows initialization under Unix.
wxWidgets initialization under Unix.
\wxheading{Remarks}
To clean up wxWindows, call wxApp::OnExit followed by the static function
wxApp::CleanUp. For example, if exiting from an MFC application that also uses wxWindows:
To clean up wxWidgets, call wxApp::OnExit followed by the static function
wxApp::CleanUp. For example, if exiting from an MFC application that also uses wxWidgets:
\begin{verbatim}
int CTheApp::ExitInstance()
@@ -362,7 +362,7 @@ int CTheApp::ExitInstance()
\func{wxAppDerivedClass\&}{wxGetApp}{\void}
This function doesn't exist in wxWindows but it is created by using
This function doesn't exist in wxWidgets but it is created by using
the \helpref{IMPLEMENT\_APP}{implementapp} macro. Thus, before using it
anywhere but in the same module where this macro is used, you must make it
available using \helpref{DECLARE\_APP}{declareapp}.
@@ -408,7 +408,7 @@ see \helpref{wxImage}{wximage}.
This function is used in wxBase only and only if you don't create
\helpref{wxApp}{wxapp} object at all. In this case you must call it from your
{\tt main()} function before calling any other wxWindows functions.
{\tt main()} function before calling any other wxWidgets functions.
If the function returns {\tt false} the initialization could not be performed,
in this case the library cannot be used and
@@ -974,7 +974,7 @@ directory doesn't exist).
This function is implemented for Win32,
Mac OS and generic Unix provided the system has {\tt statfs()} function.
This function first appeared in wxWindows 2.3.2.
This function first appeared in wxWidgets 2.3.2.
\membersection{::wxGetOSDirectory}\label{wxgetosdirectory}
@@ -1251,7 +1251,7 @@ the domain name.
Under Windows or NT, this function first looks in the environment
variable SYSTEM\_NAME; if this is not found, the entry {\bf HostName}\rtfsp
in the {\bf wxWindows} section of the WIN.INI file is tried.
in the {\bf wxWidgets} section of the WIN.INI file is tried.
The first variant of this function returns the hostname if successful or an
empty string otherwise. The second (deprecated) function returns true
@@ -1277,7 +1277,7 @@ something like "jsmith". It uniquely identifies the current user (on this system
Under Windows or NT, this function first looks in the environment
variables USER and LOGNAME; if neither of these is found, the entry {\bf UserId}\rtfsp
in the {\bf wxWindows} section of the WIN.INI file is tried.
in the {\bf wxWidgets} section of the WIN.INI file is tried.
The first variant of this function returns the login name if successful or an
empty string otherwise. The second (deprecated) function returns true
@@ -1362,7 +1362,7 @@ Returns the home directory for the given user. If the username is empty
This function returns the full user name (something like "Mr. John Smith").
Under Windows or NT, this function looks for the entry {\bf UserName}\rtfsp
in the {\bf wxWindows} section of the WIN.INI file. If PenWindows
in the {\bf wxWidgets} section of the WIN.INI file. If PenWindows
is running, the entry {\bf Current} in the section {\bf User} of
the PENWIN.INI file is used.
@@ -1623,7 +1623,7 @@ Don't confuse this macro with \helpref{\_T()}{underscoret}!
\func{const wxChar *}{\_T}{\param{const wxChar }{ch}}
This macro is exactly the same as \helpref{wxT}{wxt} and is defined in
wxWindows simply because it may be more intuitive for Windows programmers as
wxWidgets simply because it may be more intuitive for Windows programmers as
the standard Win32 headers also define it (as well as yet another name for the
same macro which is {\tt \_TEXT()}).
@@ -2276,7 +2276,7 @@ the equivalent of the following code to the start of the metafile data:
SetWindowExt(dc, maxX - minX, maxY - minY);
\end{verbatim}
This simulates the wxMM\_TEXT mapping mode, which wxWindows assumes.
This simulates the wxMM\_TEXT mapping mode, which wxWidgets assumes.
Placeable metafiles may be imported by many Windows applications, and can be
used in RTF (Rich Text Format) files.
@@ -2655,7 +2655,7 @@ the given {\bf id}.
\func{void}{wxDDECleanUp}{\void}
Called when wxWindows exits, to clean up the DDE system. This no longer needs to be
Called when wxWidgets exits, to clean up the DDE system. This no longer needs to be
called by the application.
See also \helpref{wxDDEInitialize}{wxddeinitialize}.
@@ -2672,7 +2672,7 @@ See also \helpref{wxDDEInitialize}{wxddeinitialize}.
Initializes the DDE system. May be called multiple times without harm.
This no longer needs to be called by the application: it will be called
by wxWindows if necessary.
by wxWidgets if necessary.
See also \helpref{wxDDEServer}{wxddeserver}, \helpref{wxDDEClient}{wxddeclient}, \helpref{wxDDEConnection}{wxddeconnection},\rtfsp
\helpref{wxDDECleanUp}{wxddecleanup}.
@@ -3046,7 +3046,7 @@ data in big-endian format.
\section{RTTI functions}\label{rttimacros}
wxWindows uses its own RTTI ("run-time type identification") system which
wxWidgets uses its own RTTI ("run-time type identification") system which
predates the current standard C++ RTTI and so is kept for backwards
compatibility reasons but also because it allows some things which the
standard RTTI doesn't directly support (such as creating a class from its
@@ -3054,7 +3054,7 @@ name).
The standard C++ RTTI can be used in the user code without any problems and in
general you shouldn't need to use the functions and the macros in this section
unless you are thinking of modifying or adding any wxWindows classes.
unless you are thinking of modifying or adding any wxWidgets classes.
\wxheading{See also}
@@ -3198,7 +3198,7 @@ a class that has run-time type information and two base classes. The same as IMP
\func{}{IMPLEMENT\_APP}{className}
This is used in the application class implementation file to make the application class known to
wxWindows for dynamic construction. You use this instead of
wxWidgets for dynamic construction. You use this instead of
Old form:
@@ -3421,7 +3421,7 @@ star is not appended to it.
These functions provide a variety of logging functions: see \helpref{Log classes overview}{wxlogoverview} for
further information. The functions use (implicitly) the currently active log
target, so their descriptions here may not apply if the log target is not the
standard one (installed by wxWindows in the beginning of the program).
standard one (installed by wxWidgets in the beginning of the program).
\wxheading{Include files}
@@ -3455,14 +3455,14 @@ instead.
\membersection{::wxError}\label{wxerror}
\func{void}{wxError}{\param{const wxString\& }{msg}, \param{const wxString\& }{title = "wxWindows Internal Error"}}
\func{void}{wxError}{\param{const wxString\& }{msg}, \param{const wxString\& }{title = "wxWidgets Internal Error"}}
{\bf NB:} This function is now obsolete, please use \helpref{wxLogError}{wxlogerror}
instead.
Displays {\it msg} and continues. This writes to standard error under
Unix, and pops up a message box under Windows. Used for internal
wxWindows errors. See also \helpref{wxFatalError}{wxfatalerror}.
wxWidgets errors. See also \helpref{wxFatalError}{wxfatalerror}.
\wxheading{Include files}
@@ -3471,14 +3471,14 @@ wxWindows errors. See also \helpref{wxFatalError}{wxfatalerror}.
\membersection{::wxFatalError}\label{wxfatalerror}
\func{void}{wxFatalError}{\param{const wxString\& }{msg}, \param{const wxString\& }{title = "wxWindows Fatal Error"}}
\func{void}{wxFatalError}{\param{const wxString\& }{msg}, \param{const wxString\& }{title = "wxWidgets Fatal Error"}}
{\bf NB:} This function is now obsolete, please use
\helpref{wxLogFatalError}{wxlogfatalerror} instead.
Displays {\it msg} and exits. This writes to standard error under Unix,
and pops up a message box under Windows. Used for fatal internal
wxWindows errors. See also \helpref{wxError}{wxerror}.
wxWidgets errors. See also \helpref{wxError}{wxerror}.
\wxheading{Include files}
@@ -3564,7 +3564,7 @@ If the target frame doesn't have a statusbar, the message will be lost.
\func{void}{wxVLogSysError}{\param{const char *}{formatString}, \param{va\_list }{argPtr}}
Mostly used by wxWindows itself, but might be handy for logging errors after
Mostly used by wxWidgets itself, but might be handy for logging errors after
system call (API function) failure. It logs the specified message text as well
as the last system error code ({\it errno} or {\it ::GetLastError()} depending
on the platform) and the corresponding error message. The second form
@@ -3617,7 +3617,7 @@ the mask has been previously enabled by the call to
\helpref{AddTraceMask}{wxlogaddtracemask} or by setting
\helpref{{\tt WXTRACE} environment variable}{envvars}.
The predefined string trace masks
used by wxWindows are:
used by wxWidgets are:
\begin{itemize}\itemsep=0pt
\item wxTRACE\_MemAlloc: trace memory allocation (new/delete)
@@ -3889,7 +3889,7 @@ standard usleep() function is not MT safe.
\section{Debugging macros and functions}\label{debugmacros}
Useful macros and functions for error checking and defensive programming.
wxWindows defines three families of the assert-like macros:
wxWidgets defines three families of the assert-like macros:
the wxASSERT and wxFAIL macros only do anything if \_\_WXDEBUG\_\_ is defined
(in other words, in the debug build) but disappear completely in the release
build. On the other hand, the wxCHECK macros stay event in release builds but a

6
docs/latex/wx/glcanvas.tex
View File

@@ -79,10 +79,10 @@ Constructor.
\docparam{id}{Window identifier. If -1, will automatically create an identifier.}
\docparam{pos}{Window position. wxDefaultPosition is (-1, -1) which indicates that wxWindows
\docparam{pos}{Window position. wxDefaultPosition is (-1, -1) which indicates that wxWidgets
should generate a default position for the window.}
\docparam{size}{Window size. wxDefaultSize is (-1, -1) which indicates that wxWindows should
\docparam{size}{Window size. wxDefaultSize is (-1, -1) which indicates that wxWidgets should
generate a default size for the window. If no suitable size can be found, the window will be sized to 20x20 pixels so that the window is visible but obviously not correctly sized.}
\docparam{style}{Window style.}
@@ -117,7 +117,7 @@ as the target device context for OpenGL operations.
\func{void}{SetColour}{\param{const char*}{ colour}}
Sets the current colour for this window, using the wxWindows colour database to find a named colour.
Sets the current colour for this window, using the wxWidgets colour database to find a named colour.
\membersection{wxGLCanvas::SwapBuffers}\label{wxglcanvasswapbuffers}

2
docs/latex/wx/grid.tex
View File

@@ -12,7 +12,7 @@ examples of simple and more complex applications, explains the
relationship between the various grid classes and has a summary of the
keyboard shortcuts and mouse functions provided by wxGrid.
wxGrid has been greatly expanded and redesigned for wxWindows 2.2
wxGrid has been greatly expanded and redesigned for wxWidgets 2.2
onwards. If you have been using the old wxGrid class you will probably
want to have a look at the \helpref{wxGrid classes overview}{gridoverview} to see
how things have changed. The new grid classes are reasonably backward-compatible

2
docs/latex/wx/hash.tex
View File

@@ -3,7 +3,7 @@
{\bf Please note} that this class is retained for backward compatibility
reasons; you should use \helpref{wxHashMap}{wxhashmap}.
This class provides hash table functionality for wxWindows, and for an
This class provides hash table functionality for wxWidgets, and for an
application if it wishes. Data can be hashed on an integer or string
key.

2
docs/latex/wx/hashmap.tex
View File

@@ -68,7 +68,7 @@ and VALUE\_T values.
\end{verbatim}
The HASH\_T and KEY\_EQ\_T are the types
used for the hashing function and key comparison. wxWindows provides
used for the hashing function and key comparison. wxWidgets provides
three predefined hashing functions: {\tt wxIntegerHash}
for integer types ( {\tt int}, {\tt long}, {\tt short},
and their unsigned counterparts ), {\tt wxStringHash} for strings

2
docs/latex/wx/helpevt.tex
View File

@@ -10,7 +10,7 @@ A help event is sent to the window that the user clicked on, and is propagated u
window hierarchy until the event is processed or there are no more event handlers.
The application should call wxEvent::GetId to check the identity of the clicked-on window,
and then either show some suitable help or call wxEvent::Skip if the identifier is unrecognised.
Calling Skip is important because it allows wxWindows to generate further events for ancestors
Calling Skip is important because it allows wxWidgets to generate further events for ancestors
of the clicked-on window. Otherwise it would be impossible to show help for container windows,
since processing would stop after the first window found.

6
docs/latex/wx/helpinst.tex
View File

@@ -20,7 +20,7 @@ appropriate class is aliased to the name wxHelpController for each platform, as
\begin{itemize}\itemsep=0pt
\item On Windows, wxWinHelpController is used.
\item On all other platforms, wxHtmlHelpController is used if wxHTML is
compiled into wxWindows; otherwise wxExtHelpController is used (for invoking an external
compiled into wxWidgets; otherwise wxExtHelpController is used (for invoking an external
browser).
\end{itemize}
@@ -33,7 +33,7 @@ There are currently the following help controller classes defined:
\item wxWinHelpController, for controlling Windows Help.
\item wxCHMHelpController, for controlling MS HTML Help. To use this, you need to set wxUSE\_MS\_HTML\_HELP
to 1 in setup.h and have htmlhelp.h header from Microsoft's HTML Help kit (you don't need
VC++ specific htmlhelp.lib because wxWindows loads necessary DLL at runtime and so it
VC++ specific htmlhelp.lib because wxWidgets loads necessary DLL at runtime and so it
works with all compilers).
\item wxBestHelpController, for controlling MS HTML Help or, if Microsoft's runtime is
not available, \helpref{wxHtmlHelpController}{wxhtmlhelpcontroller}. You need to provide
@@ -56,7 +56,7 @@ wxHelpControllerBase\\
\wxheading{Include files}
<wx/help.h> (wxWindows chooses the appropriate help controller class)\\
<wx/help.h> (wxWidgets chooses the appropriate help controller class)\\
<wx/helpbase.h> (wxHelpControllerBase class)\\
<wx/helpwin.h> (Windows Help controller)\\
<wx/msw/helpchm.h> (MS HTML Help controller)\\

4
docs/latex/wx/hthelpct.tex
View File

@@ -5,7 +5,7 @@
\section{\class{wxHtmlHelpController}}\label{wxhtmlhelpcontroller}
{\bf WARNING!} Although this class has an API compatible with other wxWindows
{\bf WARNING!} Although this class has an API compatible with other wxWidgets
help controllers as documented by \helpref{wxHelpController}{wxhelpcontroller}, it
is recommended that you use the enhanced capabilities of wxHtmlHelpController's API.
@@ -13,7 +13,7 @@ This help controller provides an easy way of displaying HTML help in your
application (see {\it test} sample). The help system is based on {\bf books}
(see \helpref{AddBook}{wxhtmlhelpcontrolleraddbook}). A book is a logical
section of documentation (for example "User's Guide" or "Programmer's Guide" or
"C++ Reference" or "wxWindows Reference"). The help controller can handle as
"C++ Reference" or "wxWidgets Reference"). The help controller can handle as
many books as you want.
wxHTML uses Microsoft's HTML Help Workshop project files (.hhp, .hhk, .hhc) as its

2
docs/latex/wx/htmllbox.tex
View File

@@ -6,7 +6,7 @@
%% Created: 01.06.03
%% RCS-ID: $Id$
%% Copyright: (c) 2003 Vadim Zeitlin <vadim@wxwindows.org>
%% License: wxWindows license
%% License: wxWidgets license
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\section{\class{wxHtmlListBox}}\label{wxhtmllistbox}

2
docs/latex/wx/htmlprn.tex
View File

@@ -5,7 +5,7 @@ The wxHTML library provides printing facilities with several levels of complexit
The easiest way to print an HTML document is to use
\helpref{wxHtmlEasyPrinting class}{wxhtmleasyprinting}. It lets you print HTML documents with only one
command and you don't have to worry about deriving from the wxPrintout class at all. It is only a simple wrapper around the
\helpref{wxHtmlPrintout}{wxhtmlprintout}, normal wxWindows printout class.
\helpref{wxHtmlPrintout}{wxhtmlprintout}, normal wxWidgets printout class.
And finally there is the low level class \helpref{wxHtmlDCRenderer}{wxhtmldcrenderer} which you can use to
render HTML into a rectangular area on any DC. It supports rendering into multiple rectangles with the same

14
docs/latex/wx/hworld.tex
View File

@@ -1,11 +1,11 @@
\section{wxWindows Hello World sample}\label{helloworld}
\section{wxWidgets Hello World sample}\label{helloworld}
As many people have requested a mini-sample to be published here
so that some quick judgment concerning syntax
and basic principles can be made, you can now look at wxWindows'
and basic principles can be made, you can now look at wxWidgets'
"Hello World":
You have to include wxWindows' header files, of course. This can
You have to include wxWidgets' header files, of course. This can
be done on a file by file basis (such as \#include "wx/window.h")
or using one global include (\#include "wx/wx.h"). This is
also useful on platforms which support precompiled headers such
@@ -15,7 +15,7 @@ as all major compilers on the Windows platform.
//
// file name: hworld.cpp
//
// purpose: wxWindows "Hello world"
// purpose: wxWidgets "Hello world"
//
// For compilers that support precompilation, includes "wx/wx.h".
@@ -94,7 +94,7 @@ BEGIN_EVENT_TABLE(MyFrame, wxFrame)
END_EVENT_TABLE()
\end{verbatim}
As in all programs there must be a "main" function. Under wxWindows main is implemented
As in all programs there must be a "main" function. Under wxWidgets main is implemented
using this macro, which creates an application instance and starts the program.
\begin{verbatim}
@@ -137,7 +137,7 @@ MyFrame::MyFrame(const wxString& title, const wxPoint& pos, const wxSize& size)
SetMenuBar( menuBar );
CreateStatusBar();
SetStatusText( "Welcome to wxWindows!" );
SetStatusText( "Welcome to wxWidgets!" );
}
\end{verbatim}
@@ -159,7 +159,7 @@ case a typical "About" window with information about the program.
\begin{verbatim}
void MyFrame::OnAbout(wxCommandEvent& WXUNUSED(event))
{
wxMessageBox( "This is a wxWindows' Hello world sample",
wxMessageBox( "This is a wxWidgets' Hello world sample",
"About Hello World", wxOK | wxICON_INFORMATION );
}
\end{verbatim}

14
docs/latex/wx/icon.tex
View File

@@ -126,8 +126,8 @@ Its meaning is determined by the {\it flags} parameter.}
%\twocolitem{\indexit{wxBITMAP\_TYPE\_RESOURCE}}{Load a Windows resource name.}
\end{twocollist}
The validity of these flags depends on the platform and wxWindows configuration.
If all possible wxWindows settings are used, the Windows platform supports ICO file, ICO resource,
The validity of these flags depends on the platform and wxWidgets configuration.
If all possible wxWidgets settings are used, the Windows platform supports ICO file, ICO resource,
XPM data, and XPM file. Under wxGTK, the available formats are BMP file, XPM data, XPM file, and PNG file.
Under wxMotif, the available formats are XBM data, XBM file, XPM data, XPM file.}
@@ -148,7 +148,7 @@ X and Windows.
The sixth form constructs a new icon.
The seventh form constructs an icon from pixmap (XPM) data, if wxWindows has been configured
The seventh form constructs an icon from pixmap (XPM) data, if wxWidgets has been configured
to incorporate this feature.
To use this constructor, you must first include an XPM file. For
@@ -218,7 +218,7 @@ destroyed at this point - only when the reference count is zero will the
data be deleted.
If the application omits to delete the icon explicitly, the icon will be
destroyed automatically by wxWindows when the application exits.
destroyed automatically by wxWidgets when the application exits.
Do not delete an icon that is selected into a memory device context.
@@ -267,7 +267,7 @@ The meaning of {\it name} is determined by the {\it type} parameter.}
\twocolitem{{\bf wxBITMAP\_TYPE\_XPM}}{Load an XPM bitmap file.}
\end{twocollist}
The validity of these flags depends on the platform and wxWindows configuration.}
The validity of these flags depends on the platform and wxWidgets configuration.}
\wxheading{Return value}
@@ -304,7 +304,7 @@ Saves an icon in the named file.
\twocolitem{{\bf wxBITMAP\_TYPE\_XPM}}{Save an XPM bitmap file.}
\end{twocollist}
The validity of these flags depends on the platform and wxWindows configuration.}
The validity of these flags depends on the platform and wxWidgets configuration.}
\docparam{palette}{An optional palette used for saving the icon.}
@@ -314,7 +314,7 @@ true if the operation succeeded, false otherwise.
\wxheading{Remarks}
Depending on how wxWindows has been configured, not all formats may be available.
Depending on how wxWidgets has been configured, not all formats may be available.
\wxheading{See also}

2
docs/latex/wx/iconevt.tex
View File

@@ -6,7 +6,7 @@
%% Created:
%% RCS-ID: $Id$
%% Copyright: (c) 2001 Vadim Zeitlin
%% License: wxWindows license
%% License: wxWidgets license
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\section{\class{wxIconizeEvent}}\label{wxiconizeevent}

2
docs/latex/wx/iconloc.tex
View File

@@ -6,7 +6,7 @@
%% Created: 21.06.03
%% RCS-ID: $Id$
%% Copyright: (c) 2003 Vadim Zeitlin <vadim@wxwindows.org>
%% License: wxWindows license
%% License: wxWidgets license
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\section{\class{wxIconLocation}}\label{wxiconlocation}

6
docs/latex/wx/idleevt.tex
View File

@@ -68,7 +68,7 @@ to only send idle events to windows with the wxWS\_EX\_PROCESS\_IDLE extra windo
\func{static wxIdleMode}{GetMode}{\void}
Static function returning a value specifying how wxWindows
Static function returning a value specifying how wxWidgets
will send idle events: to all windows, or only to those which specify that they
will process the events.
@@ -78,7 +78,7 @@ See \helpref{wxIdleEvent::SetMode}{wxidleeventsetmode}.
\func{void}{RequestMore}{\param{bool}{ needMore = true}}
Tells wxWindows that more processing is required. This function can be called by an OnIdle
Tells wxWidgets that more processing is required. This function can be called by an OnIdle
handler for a window or window event handler to indicate that wxApp::OnIdle should
forward the OnIdle event once more to the application windows. If no window calls this function
during OnIdle, then the application will remain in a passive event loop (not calling OnIdle) until a
@@ -102,7 +102,7 @@ Returns true if the OnIdle function processing this event requested more process
\func{static void}{SetMode}{\param{wxIdleMode }{mode}}
Static function for specifying how wxWindows will send idle events: to
Static function for specifying how wxWidgets will send idle events: to
all windows, or only to those which specify that they
will process the events.

14
docs/latex/wx/image.tex
View File

@@ -17,7 +17,7 @@ creation of a \helpref{wxMask}{wxmask} object associated to the bitmap object.
\wxheading{Alpha channel support}
Starting from wxWindows 2.5.0 wxImage supports alpha channel data, that is in
Starting from wxWidgets 2.5.0 wxImage supports alpha channel data, that is in
addition to a byte for the red, green and blue colour components for each pixel
it also stores a byte representing the pixel opacity. The alpha value of $0$
corresponds to a transparent pixel (null opacity) while the value of $255$
@@ -154,7 +154,7 @@ the GIF and TIFF handler and as the largest and most colourful one by the ICO ha
\wxheading{Remarks}
Depending on how wxWindows has been configured, not all formats may be available.
Depending on how wxWidgets has been configured, not all formats may be available.
Note: any handler other than BMP must be previously
initialized with \helpref{wxImage::AddHandler}{wximageaddhandler} or
@@ -229,7 +229,7 @@ returns true if the current image handlers can read this file
Deletes all image handlers.
This function is called by wxWindows on exit.
This function is called by wxWidgets on exit.
\membersection{wxImage::ComputeHistogram}\label{wximagecomputehistogram}
@@ -591,7 +591,7 @@ Returns true if the given option is present. The function is case-insensitive to
Internal use only. Adds standard image format handlers. It only install BMP
for the time being, which is used by wxBitmap.
This function is called by wxWindows on startup, and shouldn't be called by
This function is called by wxWidgets on startup, and shouldn't be called by
the user.
\wxheading{See also}
@@ -660,7 +660,7 @@ the GIF and TIFF handler and as the largest and most colourful one by the ICO ha
\wxheading{Remarks}
Depending on how wxWindows has been configured, not all formats may be available.
Depending on how wxWidgets has been configured, not all formats may be available.
Note: you can use \helpref{GetOptionInt}{wximagegetoptionint} to get the
hotspot for loaded cursor file:
@@ -815,7 +815,7 @@ true if the operation succeeded, false otherwise.
\wxheading{Remarks}
Depending on how wxWindows has been configured, not all formats may be available.
Depending on how wxWidgets has been configured, not all formats may be available.
Note: you can use \helpref{GetOptionInt}{wximagegetoptionint} to set the
hotspot before saving an image into a cursor file (default hotspot is in
@@ -1046,7 +1046,7 @@ application initialisation.
This software is based in part on the work of the Independent JPEG Group.
(Applies when wxWindows is linked with JPEG support. wxJPEGHandler uses libjpeg
(Applies when wxWidgets is linked with JPEG support. wxJPEGHandler uses libjpeg
created by IJG.)
\wxheading{Derived from}

8
docs/latex/wx/keyevent.tex
View File

@@ -2,7 +2,7 @@
This event class contains information about keypress (character) events.
Notice that there are three different kinds of keyboard events in wxWindows:
Notice that there are three different kinds of keyboard events in wxWidgets:
key down and up events and char events. The difference between the first two
is clear - the first corresponds to a key press and the second to a key
release - otherwise they are identical. Just note that if the key is
@@ -37,7 +37,7 @@ same key code {\tt 'a'} as usual but the char event will have key code of
$1$, the ASCII value of this key combination.
You may discover how the other keys on your system behave interactively by
running the \helpref{text}{sampletext} wxWindows sample and pressing some keys
running the \helpref{text}{sampletext} wxWidgets sample and pressing some keys
in any of the text controls shown in it.
{\bf Note:} If a key down ({\tt EVT\_KEY\_DOWN}) event is caught and
@@ -46,10 +46,10 @@ char event ({\tt EVT\_CHAR}) will not happen. This is by design and
enables the programs that handle both types of events to be a bit
simpler.
{\bf Note for Windows programmers:} The key and char events in wxWindows are
{\bf Note for Windows programmers:} The key and char events in wxWidgets are
similar to but slightly different from Windows {\tt WM\_KEYDOWN} and
{\tt WM\_CHAR} events. In particular, Alt-x combination will generate a char
event in wxWindows (unless it is used as an accelerator).
event in wxWidgets (unless it is used as an accelerator).
{\bf Tip:} be sure to call {\tt event.Skip()} for events that you don't process in
key event function, otherwise menu shortcuts may cease to work under Windows.

14
docs/latex/wx/libs.tex
View File

@@ -2,11 +2,11 @@
\setheader{{\it CHAPTER \thechapter}}{}{}{}{}{{\it CHAPTER \thechapter}}%
\setfooter{\thepage}{}{}{}{}{\thepage}%
Starting from version 2.5.0 wxWindows can be built either as a single large
Starting from version 2.5.0 wxWidgets can be built either as a single large
library (this is called the {\it monolithic build}) or as several smaller
libraries ({\it multilib build}). Multilib build is the default.
wxWindows library is divided into libraries briefly described below. This
wxWidgets library is divided into libraries briefly described below. This
diagram show dependencies between them:
\begin{center}
@@ -15,8 +15,8 @@ diagram show dependencies between them:
{\large {\bf wxBase}}
Every wxWindows application must link against this library. It contains
mandatory classes that any wxWindows code depends on (e.g.
Every wxWidgets application must link against this library. It contains
mandatory classes that any wxWidgets code depends on (e.g.
\helpref{wxString}{wxstring}) and portability classes that abstract
differences between platforms. wxBase can be used to develop console mode
applications, it does not require any GUI libraries or running X Window System
@@ -45,13 +45,13 @@ This library contains simple classes for parsing XML documents. Note that
their API {\em will} change in the future and backward
compatibility will not be preserved. Use of this library in your applications
is not recommended, it is only meant for use by XML resources system. Future
versions of wxWindows will contain new XML handling classes with DOM-like API.
versions of wxWidgets will contain new XML handling classes with DOM-like API.
Requires wxBase.
{\large {\bf wxCore}}
Basic GUI classes such as GDI classes or controls are in this library. All
wxWindows GUI applications must link against this library, only console mode
wxWidgets GUI applications must link against this library, only console mode
applications don't.
{\large {\bf wxAdvanced}}
@@ -79,7 +79,7 @@ Requires wxCore and wxBase.
{\large {\bf wxGL}}
This library contains \helpref{wxGLCanvas}{wxglcanvas} class for integrating
OpenGL library with wxWindows. Unlike all others, this library is {\em not}
OpenGL library with wxWidgets. Unlike all others, this library is {\em not}
part of the monolithic library, it is always built as separate library.
Requires wxCore and wxBase.

6
docs/latex/wx/list.tex
View File

@@ -1,19 +1,19 @@
\section{\class{wxList}}\label{wxlist}
wxList classes provide linked list functionality for wxWindows, and for an
wxList classes provide linked list functionality for wxWidgets, and for an
application if it wishes. Depending on the form of constructor used, a list
can be keyed on integer or string keys to provide a primitive look-up ability,
but please note that this feature is {\bf deprecated}.
See \helpref{wxHashMap}{wxhashmap}\rtfsp for a faster method of storage
when random access is required.
While wxList class in the previous versions of wxWindows only could contain
While wxList class in the previous versions of wxWidgets only could contain
elements of type wxObject and had essentially untyped interface (thus allowing
you to put apples in the list and read back oranges from it), the new wxList
classes family may contain elements of any type and has much more strict type
checking. Unfortunately, it also requires an additional line to be inserted in
your program for each list class you use (which is the only solution short of
using templates which is not done in wxWindows because of portability issues).
using templates which is not done in wxWidgets because of portability issues).
The general idea is to have the base class wxListBase working with {\it void *}
data but make all of its dangerous (because untyped) functions protected, so

2
docs/latex/wx/listbook.tex
View File

@@ -6,7 +6,7 @@
%% Created: 22.08.03
%% RCS-ID: $Id$
%% Copyright: (c) 2003 Vadim Zeitlin <vadim@wxwindows.org>
%% License: wxWindows license
%% License: wxWidgets license
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\section{\class{wxListbook}}\label{wxlistbook}

2
docs/latex/wx/listview.tex
View File

@@ -6,7 +6,7 @@
%% Created: 07.11.02
%% RCS-ID: $Id$
%% Copyright: (c) 2002 Vadim Zeitlin <vadim@wxwindows.org>
%% License: wxWindows license
%% License: wxWidgets license
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\section{\class{wxListView}}\label{wxlistview}

6
docs/latex/wx/locale.tex
View File

@@ -3,7 +3,7 @@
wxLocale class encapsulates all language-dependent settings and is a
generalization of the C locale concept.
In wxWindows this class manages message catalogs which contain the translations
In wxWidgets this class manages message catalogs which contain the translations
of the strings used to the current language.
\perlnote{In wxPerl you can't use the '\_' function name, so
@@ -561,7 +561,7 @@ language (see \helpref{GetSystemLanguage}{wxlocalegetsystemlanguage}).}
\docparam{flags}{Combination of the following:
\begin{twocollist}\itemsep=0pt
\twocolitem{\windowstyle{wxLOCALE\_LOAD\_DEFAULT}}{Load the message catalog
for the given locale containing the translations of standard wxWindows messages
for the given locale containing the translations of standard wxWidgets messages
automatically.}
\twocolitem{\windowstyle{wxLOCALE\_CONV\_ENCODING}}{Automatically convert message
catalogs to platform's default encoding. Note that it will do only basic
@@ -580,7 +580,7 @@ directory prefix when looking for the message catalog files.}
platform-specific.}
\docparam{bLoadDefault}{May be set to false to prevent loading of the message catalog
for the given locale containing the translations of standard wxWindows messages.
for the given locale containing the translations of standard wxWidgets messages.
This parameter would be rarely used in normal circumstances.}
\docparam{bConvertEncoding}{May be set to true to do automatic conversion of message

16
docs/latex/wx/log.tex
View File

@@ -6,12 +6,12 @@
%% Created: some time ago
%% RCS-ID: $Id$
%% Copyright: (c) 1997-2001 Vadim Zeitlin
%% License: wxWindows license
%% License: wxWidgets license
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\section{\class{wxLog}}\label{wxlog}
wxLog class defines the interface for the {\it log targets} used by wxWindows
wxLog class defines the interface for the {\it log targets} used by wxWidgets
logging functions as explained in the \helpref{wxLog overview}{wxlogoverview}.
The only situations when you need to directly use this class is when you want
to derive your own log target because the existing ones don't satisfy your
@@ -23,7 +23,7 @@ completely) the timestamp on the messages.
Otherwise, it is completely hidden behind the {\it wxLogXXX()} functions and
you may not even know about its existence.
See \helpref{log overview}{wxlogoverview} for the descriptions of wxWindows
See \helpref{log overview}{wxlogoverview} for the descriptions of wxWidgets
logging facilities.
\wxheading{Derived from}
@@ -456,9 +456,9 @@ object was created.
\section{\class{wxLogGui}}\label{wxloggui}
This is the default log target for the GUI wxWindows applications. It is passed
This is the default log target for the GUI wxWidgets applications. It is passed
to \helpref{wxLog::SetActiveTarget}{wxlogsetactivetarget} at the program
startup and is deleted by wxWindows during the program shut down.
startup and is deleted by wxWidgets during the program shut down.
\wxheading{Derived from}
@@ -483,7 +483,7 @@ Default constructor.
This class allows to temporarily suspend logging. All calls to the log
functions during the life time of an object of this class are just ignored.
In particular, it can be used to suppress the log messages given by wxWindows
In particular, it can be used to suppress the log messages given by wxWidgets
itself but it should be noted that it is rarely the best way to cope with this
problem as {\bf all} log messages are suppressed, even if they indicate a
completely different error than the one the programmer wanted to suppress.
@@ -578,7 +578,7 @@ Default ctor installs this object as the current active log target.
This class can be used to redirect the log messages to a C file stream (not to
be confused with C++ streams). It is the default log target for the non-GUI
wxWindows applications which send all the output to {\tt stderr}.
wxWidgets applications which send all the output to {\tt stderr}.
\wxheading{Derived from}
@@ -607,7 +607,7 @@ Constructs a log target which sends all the log messages to the given
This class can be used to redirect the log messages to a C++ stream.
Please note that this class is only available if wxWindows was compiled with
Please note that this class is only available if wxWidgets was compiled with
the standard iostream library support ({\tt wxUSE\_STD\_IOSTREAM} must be on).
\wxheading{Derived from}

2
docs/latex/wx/longlong.tex
View File

@@ -6,7 +6,7 @@
%% Created: 07.03.00
%% RCS-ID: $Id$
%% Copyright: (c) Vadim Zeitlin
%% License: wxWindows license
%% License: wxWidgets license
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\section{\class{wxLongLong}}\label{wxlonglong}

20
docs/latex/wx/manual.tex
View File

@@ -26,7 +26,7 @@
%\special{!/@scaleunit 1 def}
\parskip=10pt
\parindent=0pt
\title{wxWindows 2.5.1: A portable C++ and Python GUI toolkit}
\title{wxWidgets 2.5.1: A portable C++ and Python GUI toolkit}
\winhelponly{\author{by Julian Smart et al
%\winhelponly{\\$$\image{1cm;0cm}{wxwin.wmf}$$}
}}
@@ -47,7 +47,7 @@ Robin Dunn, et al}
% A special table of contents for the WinHelp manual
\begin{comment}
\winhelponly{
\chapter{wxWindows class library reference}\label{winhelpcontents}
\chapter{wxWidgets class library reference}\label{winhelpcontents}
\centerline{
%\image{}{wxwin.wmf}
@@ -62,19 +62,19 @@ Robin Dunn, et al}
\image{}{book1.bmp} \helpref{Topic overviews}{overviews}
\image{}{hand1.bmp} \helpref{Guide to wxWindows}{wxwinchapters}
\image{}{hand1.bmp} \helpref{Guide to wxWidgets}{wxwinchapters}
}
\sethotspotcolour{on}%
\sethotspotunderline{on}%
\chapter*{Overview of wxWindows}\label{wxwinchapters}
\chapter*{Overview of wxWidgets}\label{wxwinchapters}
\helpref{Introduction}{introduction}\\
%\helpref{Resource guide}{resguide}\\
%\helpref{Comparison with other GUI models}{comparison}\\
%\helpref{Multi-platform development with wxWindows}{multiplat}\\
%\helpref{Multi-platform development with wxWidgets}{multiplat}\\
%\helpref{Tutorial}{tutorial}\\
\helpref{The wxWindows resource system}{resourceformats}\\
\helpref{The wxWidgets resource system}{resourceformats}\\
\helpref{Utilities}{utilities}\\
\helpref{Programming strategies}{strategies}\\
\helpref{Bugs and future directions}{bugs}\\
@@ -88,14 +88,14 @@ Robin Dunn, et al}
\begin{center}
Copyright (c) 1992-2002 Julian Smart, Robert Roebling, Vadim Zeitlin and other
members of the wxWindows team\\
members of the wxWidgets team\\
Portions (c) 1996 Artificial Intelligence Applications Institute\\
\end{center}
Please also see the wxWindows license files (preamble.txt, lgpl.txt, gpl.txt, license.txt,
Please also see the wxWidgets license files (preamble.txt, lgpl.txt, gpl.txt, license.txt,
licendoc.txt) for conditions of software and documentation use.
\section*{wxWindows Library License, Version 3}
\section*{wxWidgets Library License, Version 3}
Copyright (c) 1992-2004 Julian Smart, Robert Roebling, Vadim Zeitlin et al.
@@ -126,7 +126,7 @@ EXCEPTION NOTICE
1. As a special exception, the copyright holders of this library give
permission for additional uses of the text contained in this release of
the library as licensed under the wxWindows Library License, applying
the library as licensed under the wxWidgets Library License, applying
either version 3 of the License, or (at your option) any later version of
the License as published by the copyright holders of version 3 of the
License document.

20
docs/latex/wx/manual2e.tex
View File

@@ -31,7 +31,7 @@
%\special{!/@scaleunit 1 def}
\parskip=10pt
\parindent=0pt
\title{wxWindows 2.4.1: A portable C++ and Python GUI toolkit}
\title{wxWidgets 2.4.1: A portable C++ and Python GUI toolkit}
\winhelponly{\author{by Julian Smart et al
%\winhelponly{\\$$\image{1cm;0cm}{wxwin.wmf}$$}
}}
@@ -52,7 +52,7 @@ Robin Dunn, et al}
% A special table of contents for the WinHelp manual
\begin{comment}
\winhelponly{
\chapter{wxWindows class library reference}\label{winhelpcontents}
\chapter{wxWidgets class library reference}\label{winhelpcontents}
\centerline{
%\image{}{wxwin.wmf}
@@ -67,19 +67,19 @@ Robin Dunn, et al}
\image{}{book1.bmp} \helpref{Topic overviews}{overviews}
\image{}{hand1.bmp} \helpref{Guide to wxWindows}{wxwinchapters}
\image{}{hand1.bmp} \helpref{Guide to wxWidgets}{wxwinchapters}
}
\sethotspotcolour{on}%
\sethotspotunderline{on}%
\chapter*{Overview of wxWindows}\label{wxwinchapters}
\chapter*{Overview of wxWidgets}\label{wxwinchapters}
\helpref{Introduction}{introduction}\\
%\helpref{Resource guide}{resguide}\\
%\helpref{Comparison with other GUI models}{comparison}\\
%\helpref{Multi-platform development with wxWindows}{multiplat}\\
%\helpref{Multi-platform development with wxWidgets}{multiplat}\\
%\helpref{Tutorial}{tutorial}\\
\helpref{The wxWindows resource system}{resourceformats}\\
\helpref{The wxWidgets resource system}{resourceformats}\\
\helpref{Utilities}{utilities}\\
\helpref{Programming strategies}{strategies}\\
\helpref{Bugs and future directions}{bugs}\\
@@ -93,14 +93,14 @@ Robin Dunn, et al}
\begin{center}
Copyright (c) 1992-2002 Julian Smart, Robert Roebling, Vadim Zeitlin and other
members of the wxWindows team\\
members of the wxWidgets team\\
Portions (c) 1996 Artificial Intelligence Applications Institute\\
\end{center}
Please also see the wxWindows license files (preamble.txt, lgpl.txt, gpl.txt, license.txt,
Please also see the wxWidgets license files (preamble.txt, lgpl.txt, gpl.txt, license.txt,
licendoc.txt) for conditions of software and documentation use.
\section*{wxWindows Library License, Version 3}
\section*{wxWidgets Library License, Version 3}
Copyright (c) 1992-2002 Julian Smart, Robert Roebling, Vadim Zeitlin et al.
@@ -131,7 +131,7 @@ EXCEPTION NOTICE
1. As a special exception, the copyright holders of this library give
permission for additional uses of the text contained in this release of
the library as licensed under the wxWindows Library License, applying
the library as licensed under the wxWidgets Library License, applying
either version 3 of the License, or (at your option) any later version of
the License as published by the copyright holders of version 3 of the
License document.

2
docs/latex/wx/maxzevt.tex
View File

@@ -6,7 +6,7 @@
%% Created:
%% RCS-ID: $Id$
%% Copyright: (c) 2001 Vadim Zeitlin
%% License: wxWindows license
%% License: wxWidgets license
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\section{\class{wxMaximizeEvent}}\label{wxmaximizeevent}

2
docs/latex/wx/mcaptevt.tex
View File

@@ -46,5 +46,5 @@ Constructor.
\constfunc{wxWindow*}{GetCapturedWindow}{\void}
Returns the window that gained the capture, or NULL if it was a non-wxWindows window.
Returns the window that gained the capture, or NULL if it was a non-wxWidgets window.

12
docs/latex/wx/mdi.tex
View File

@@ -36,7 +36,7 @@ See also \helpref{window styles overview}{windowstyles}.
\wxheading{Remarks}
Although internally an MDI child frame is a child of the MDI client window, in wxWindows
Although internally an MDI child frame is a child of the MDI client window, in wxWidgets
you create it as a child of \helpref{wxMDIParentFrame}{wxmdiparentframe}. You can usually
forget that the client window exists.
@@ -77,10 +77,10 @@ Constructor, creating the window.
\docparam{title}{The caption to be displayed on the frame's title bar.}
\docparam{pos}{The window position. A value of (-1, -1) indicates a default position, chosen by
either the windowing system or wxWindows, depending on platform.}
either the windowing system or wxWidgets, depending on platform.}
\docparam{size}{The window size. A value of (-1, -1) indicates a default size, chosen by
either the windowing system or wxWindows, depending on platform.}
either the windowing system or wxWidgets, depending on platform.}
\docparam{style}{The window style. See \helpref{wxMDIChildFrame}{wxmdichildframe}.}
@@ -311,10 +311,10 @@ Constructor, creating the window.
\docparam{title}{The caption to be displayed on the frame's title bar.}
\docparam{pos}{The window position. A value of (-1, -1) indicates a default position, chosen by
either the windowing system or wxWindows, depending on platform.}
either the windowing system or wxWidgets, depending on platform.}
\docparam{size}{The window size. A value of (-1, -1) indicates a default size, chosen by
either the windowing system or wxWindows, depending on platform.}
either the windowing system or wxWidgets, depending on platform.}
\docparam{style}{The window style. See \helpref{wxMDIParentFrame}{wxmdiparentframe}.}
@@ -469,7 +469,7 @@ Returns the window being used as the toolbar for this frame.
\constfunc{wxMenu*}{GetWindowMenu}{\void}
Returns the current Window menu (added by wxWindows to the menubar). This function
Returns the current Window menu (added by wxWidgets to the menubar). This function
is available under Windows only.
\membersection{wxMDIParentFrame::OnCreateClient}\label{wxmdiparentframeoncreateclient}

2
docs/latex/wx/menu.tex
View File

@@ -12,7 +12,7 @@ associated command but just makes a separator line appear in the menu.
Menu items may be either normal items, check items or radio items. Normal items
don't have any special properties while the check items have a boolean flag
associated to them and they show a checkmark in the menu when the flag is set.
wxWindows automatically toggles the flag value when the item is clicked and its
wxWidgets automatically toggles the flag value when the item is clicked and its
value may be retrieved using either \helpref{IsChecked}{wxmenuischecked} method
of wxMenu or wxMenuBar itself or by using
\helpref{wxEvent::IsChecked}{wxcommandeventischecked} when you get the menu

2
docs/latex/wx/metafile.tex
View File

@@ -1,7 +1,7 @@
\section{\class{wxMetafile}}\label{wxmetafile}
A {\bf wxMetafile} represents the MS Windows metafile object, so metafile
operations have no effect in X. In wxWindows, only sufficient functionality
operations have no effect in X. In wxWidgets, only sufficient functionality
has been provided for copying a graphic to the clipboard; this may be extended
in a future version. Presently, the only way of creating a metafile
is to use a wxMetafileDC.

4
docs/latex/wx/minifram.tex
View File

@@ -76,10 +76,10 @@ always be displayed on top of the parent window on Windows.}
\docparam{title}{The caption to be displayed on the frame's title bar.}
\docparam{pos}{The window position. A value of (-1, -1) indicates a default position, chosen by
either the windowing system or wxWindows, depending on platform.}
either the windowing system or wxWidgets, depending on platform.}
\docparam{size}{The window size. A value of (-1, -1) indicates a default size, chosen by
either the windowing system or wxWindows, depending on platform.}
either the windowing system or wxWidgets, depending on platform.}
\docparam{style}{The window style. See \helpref{wxMiniFrame}{wxminiframe}.}

4
docs/latex/wx/mirrordc.tex
View File

@@ -6,7 +6,7 @@
%% Created: 21.07.03
%% RCS-ID: $Id$
%% Copyright: (c) 2003 Vadim Zeitlin
%% License: wxWindows license
%% License: wxWidgets license
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\section{\class{wxMirrorDC}}\label{wxmirrordc}
@@ -17,7 +17,7 @@ without changes (no mirroring takes place) or exchanges {\it x} and {\it y}
coordinates which makes it possible to reuse the same code to draw a figure and
its mirror -- i.e. reflection related to the diagonal line $x == y$.
wxMirrorDC has been added in wxWindows version 2.5.0.
wxMirrorDC has been added in wxWidgets version 2.5.0.
\wxheading{Derived from}

Some files were not shown because too many files have changed in this diff Show More