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/branches/WX_2_4_BRANCH@27091 c3d73ce0-8a6f-49c7-b76d-6d57e0e08775
This commit is contained in:
Julian Smart
2004-05-04 08:52:33 +00:00
parent 03d21d9053
commit 74ca941903
229 changed files with 1170 additions and 1138 deletions
Download Patch File Download Diff File Expand all files Collapse all files

34
docs/changes.txt
View File

@@ -1,5 +1,5 @@
wxWindows 2 Change Log
----------------------
wxWidgets Change Log
--------------------
INCOMPATIBLE CHANGES SINCE 2.2.x
================================
@@ -15,7 +15,7 @@ INCOMPATIBLE CHANGES SINCE 2.2.x
2.6 release.
NB: if you want to build your program with different major versions
of wxWindows you will probably find the wxCHECK_VERSION() macro
of wxWidgets you will probably find the wxCHECK_VERSION() macro
(see the documentation) useful.
@@ -205,7 +205,6 @@ Unix:
- typo in configure which broke AIX build fixed (Swengtoo)
- fixed priorities of mailcap entries (David Hart)
>>>>>>> 1.212.2.99
wxMSW:
- strip ampersands from strings returned by wxMenuBar::GetLabelTop()
@@ -213,6 +212,7 @@ wxMSW:
- fixed hang (sometimes) in wxThread::Delete() (Carl-Friedrich Braun)
- wxLongLong formatting with MinGW corrected
- wxFileDialog now returns correct filter index for multiple-file dialogs
- Fixed a bug in wxSpinCtrl::DoGetBestSize that would make wxSpinCtrl too tall
wxGTK:
@@ -223,7 +223,7 @@ wxOS2:
- fixed bug in Refresh (was not taking reversed coordinate system into
account, so failed for most generic controls)
- partly fixed wxMouseEvent (reversed coordinate system again, handling of
CTRL and SHIFT keys. ALT still doesn't work as expected by wxWindows, though)
CTRL and SHIFT keys. ALT still doesn't work as expected by wxWidgets, though)
2.4.2
@@ -296,7 +296,7 @@ All:
- accept '\r' as delimiter when parsing dates
- fixed duplicate wxFontEncoding values
- wxFileConfig now always uses UTF-8 to store settings in Unicode build;
it will be possible to set different charset in wxWindows >= 2.5.0
it will be possible to set different charset in wxWidgets >= 2.5.0
- added wxFileName::MakeAbsolute
- bugs in wxCalCtrl fixed (year not being updated)
@@ -349,7 +349,7 @@ wxMSW:
sunken border under XP
- partial fix for wxNotebook pages looking bad under XP: wxUSE_UXTHEME
enables XP theme engine code, and wxUSE_UXTHEME_AUTO tells
wxWindows to use the theme tab colour for control backgrounds.
wxWidgets to use the theme tab colour for control backgrounds.
Proper XP theme support is planned for 2.6
- disable wxNB_RIGHT, wxNB_LEFT, wxNB_BOTTOM notebook styles
if the version of CommCtl doesn't support it (XP)
@@ -460,10 +460,10 @@ wxBase:
Unix (Base/GUI):
- wxWindows may be built using BSD and Solaris (and possibly other) make
- wxWidgets may be built using BSD and Solaris (and possibly other) make
programs and not only GNU make
- wxTCP-based IPC classes now support communicating over Unix domain sockets
- wxWindows may be built as a dynamic shared library under Darwin / Mac OS X
- wxWidgets may be built as a dynamic shared library under Darwin / Mac OS X
lazy linking issues have been solved by linking a single module (.o) into
the shared library (two step link using distrib/mac/shared-ld-sh)
- fixed thread priority setting under Linux
@@ -475,7 +475,7 @@ All (GUI):
- implemented radio menu items and radio toolbar buttons
- added possibility to show text in the toolbar buttons
- added wxArtProvider class that can be used to customize the look of standard
wxWindows dialogs
wxWidgets dialogs
- significantly improved native font support
- wxImage::ComputeHistogram() now uses wxImageHistogram instead of type-unsafe
wxHashTable
@@ -517,11 +517,11 @@ wxMSW:
- fixed multiple bugs in wxExecute() with IO redirection
- refresh the buttons properly when the window is resized (Hans Van Leemputten)
- huge (40*) speed up in wxMask::Create()
- changing wxWindows styles also changes the underlying Windows window style
- changing wxWidgets styles also changes the underlying Windows window style
- wxTreeCtrl supports wxTR_HIDE_ROOT style (George Policello)
- fixed flicker in wxTreeCtrl::SetItemXXX()
- fixed redraw problems in dynamically resized wxStaticText
- improvements to wxWindows applications behaviour when the system colours
- improvements to wxWidgets applications behaviour when the system colours
are changed
- choose implicit parent for the dialog boxes better
- fixed wxProgressDialog for ranges > 65535
@@ -710,7 +710,7 @@ wxMSW:
- Fixed wxFrame::SetClientSize() with toolbar bug
- Added mousewheel processing
- Added wxSystemSettings::Get/SetOption so we can configure
wxWindows at run time; used this to implement no-maskblt option
wxWidgets at run time; used this to implement no-maskblt option
in wxDC
- Fixed bug when using MDIS_ALLCHILDSTYLES style: so now MDI
child frame styles are honoured
@@ -980,7 +980,7 @@ wxHTML:
fixed handling of relative and absolute font sizes in <font size>
NOTE: for changes after wxWindows 2.1.0 b4, please see the CVS
NOTE: for changes after wxWidgets 2.1.0 b4, please see the CVS
change log.
2.1.0, b4, May 9th 1999
@@ -1078,7 +1078,7 @@ wxMSW:
- Makefiles for more compilers and samples; Cygwin makefiles
rationalised.
- Added VC++ project file for compiling wxWindows as DLL.
- Added VC++ project file for compiling wxWidgets as DLL.
wxMotif:
@@ -1406,7 +1406,7 @@ wxMSW:
- Added wxJoystick class and event handling, and simple demo.
- Added simple wxWave class. Needs Stop() function.
- Added wxModule (module.h/module.cpp) to allow definition
of modules to be initialized and cleaned up on wxWindows
of modules to be initialized and cleaned up on wxWidgets
startup/exit.
- Start of Mingw32 compatibility (see minimal and dialogs samples
makefile.m95 files, and install.txt).
@@ -1448,7 +1448,7 @@ wxMSW:
- Added wxTaskBarIcon (taskbar.cpp/h, plus samples/taskbar)
to allow maintenance of an icon in the Windows 95 taskbar
tray area.
- Got MFC sample working (MFC and wxWindows in the same
- Got MFC sample working (MFC and wxWidgets in the same
application), partly by tweaking ntwxwin.mak settings.
- Got DLL compilation working again (VC++).
- Changed wxProp/Dialog Editor filenames.

10
docs/html/faq.htm
View File

@@ -2,7 +2,7 @@
<html>
<head>
<title>wxWindows 2 FAQ</title>
<title>wxWidgets 2 FAQ</title>
</head>
<body bgcolor=#ffffff text=#000000 vlink="#00376a" link="#00529c" alink="#313063">
@@ -13,7 +13,7 @@
<tr>
<td bgcolor="#004080" align=left height=24 background="images/bluetitlegradient.gif">
<font size=+1 face="arial, lucida sans, helvetica" color="#ffffff">
<b>wxWindows 2 FAQ</b>
<b>wxWidgets 2 FAQ</b>
</font>
</td>
</tr>
@@ -21,7 +21,7 @@
<p>
Welcome to the wxWindows FAQ. Please select a category:<p>
Welcome to the wxWidgets FAQ. Please select a category:<p>
<ul>
<li><a href="faqgen.htm">General questions</a>
@@ -36,10 +36,10 @@ Welcome to the wxWindows FAQ. Please select a category:<p>
<p>
For further information, please see the
<a href="http://www.wxwindows.org" target=_top>wxWindows Web site</a>,
<a href="http://www.wxwindows.org" target=_top>wxWidgets Web site</a>,
<a href="http://wiki.wxwindows.org" target=_top>wxWiki</a>
and install.txt (per port), todo.txt (per port), and bugs.txt (all ports) files
in your wxWindows installation.
in your wxWidgets installation.
<p>
</font>

142
docs/html/faqgen.htm
View File

@@ -2,7 +2,7 @@
<HTML>
<HEAD>
<TITLE>wxWindows 2 FAQ: General</TITLE>
<TITLE>wxWidgets 2 FAQ: General</TITLE>
</HEAD>
<BODY BGCOLOR=#FFFFFF TEXT=#000000 VLINK="#00376A" LINK="#00529C" ALINK="#313063">
@@ -13,7 +13,7 @@
<tr>
<td bgcolor="#004080" align=left height=24 background="images/bluetitlegradient.gif">
<font size=+1 face="Arial, Lucida Sans, Helvetica" color="#FFFFFF">
<b>wxWindows 2 FAQ: General</b>
<b>wxWidgets 2 FAQ: General</b>
</font>
</td>
</tr>
@@ -25,17 +25,17 @@ See also <a href="faq.htm">top-level FAQ page</a>.
<hr>
<h3>List of questions in this category</h3>
<ul>
<li><a href="#whatis">What is wxWindows?</a></li>
<li><a href="#licence">Can I use wxWindows 2 for both proprietary projects, and GPL&#39;ed projects?</a></li>
<li><a href="#whatis">What is wxWidgets?</a></li>
<li><a href="#licence">Can I use wxWidgets 2 for both proprietary projects, and GPL&#39;ed projects?</a></li>
<li><a href="#support">Is there support?</a></li>
<li><a href="#users">Who uses wxWindows?</a></li>
<li><a href="#platforms">What platforms are supported by wxWindows?</a></li>
<li><a href="#specific">How does wxWindows support platform-specific features?</a></li>
<li><a href="#stl">Does wxWindows use STL? or the standard string class?</a></li>
<li><a href="#richedit">Is there a rich edit/markup widget for wxWindows?</a></ li>
<li><a href="#exceptions">How to use C++ exceptions with wxWindows?</a></ li>
<li><a href="#dev">How is wxWindows being developed?</a></li>
<li><a href="#distrib">How is wxWindows distributed?</a></li>
<li><a href="#users">Who uses wxWidgets?</a></li>
<li><a href="#platforms">What platforms are supported by wxWidgets?</a></li>
<li><a href="#specific">How does wxWidgets support platform-specific features?</a></li>
<li><a href="#stl">Does wxWidgets use STL? or the standard string class?</a></li>
<li><a href="#richedit">Is there a rich edit/markup widget for wxWidgets?</a></ li>
<li><a href="#exceptions">How to use C++ exceptions with wxWidgets?</a></ li>
<li><a href="#dev">How is wxWidgets being developed?</a></li>
<li><a href="#distrib">How is wxWidgets distributed?</a></li>
<li><a href="#future">What are the plans for the future?</a></li>
<li><a href="#base">What is wxBase?</a></li>
<li><a href="#univ">What is wxUniversal?</a></li>
@@ -45,10 +45,10 @@ See also <a href="faq.htm">top-level FAQ page</a>.
</ul>
<hr>
<H3><a name="whatis">What is wxWindows?</a></H3>
<H3><a name="whatis">What is wxWidgets?</a></H3>
wxWindows is a class library that allows you to compile graphical C++ programs on a range of
different platforms. wxWindows defines a common API across platforms, but uses the native graphical user interface (GUI) on each platform,
wxWidgets is a class library that allows you to compile graphical C++ programs on a range of
different platforms. wxWidgets defines a common API across platforms, but uses the native graphical user interface (GUI) on each platform,
so your program will take on the native &#39;look and feel&#39; that users are familiar with.<P>
Although GUI applications are mostly built programmatically, there are several dialog editors to help
@@ -56,32 +56,32 @@ build attractive dialogs and panels. Robert Roebling&#39;s <a href="http://www.r
and Anthemion Software's <a href="http://www.anthemion.co.uk/dialogblocks/" target=_new>DialogBlocks</a>
are two commercial examples, but there are others: see the <a href="lnk_tools.htm">Useful Tools</a> page.<P>
You don&#39;t have to use C++ to use wxWindows: there is a <a href="http://wxpython.org">Python interface</a> for wxWindows 2,
You don&#39;t have to use C++ to use wxWidgets: there is a <a href="http://wxpython.org">Python interface</a> for wxWidgets 2,
and also a <a href="http://wxperl.sourceforge.net" target=_top>Perl interface</a>.
<P>
<h3><a name="licence">Can I use wxWindows 2 for both proprietary (commercial) projects, and GPL&#39;ed projects?</a></h3>
<h3><a name="licence">Can I use wxWidgets 2 for both proprietary (commercial) projects, and GPL&#39;ed projects?</a></h3>
Yes. Please see the <a href="newlicen.htm">licence</a> for details, but basically
you can distribute proprietary binaries without distributing any source code, and neither will wxWindows
you can distribute proprietary binaries without distributing any source code, and neither will wxWidgets
conflict with GPL code you may be using or developing with it.
<P>
The conditions for using wxWindows 2 are the same whether you are a personal, academic
The conditions for using wxWidgets 2 are the same whether you are a personal, academic
or commercial developer.
<P>
<h3><a name="support">Is there support?</a></h3>
No official support, but the mailing list is very helpful and some people say that
wxWindows support is better than for much commercial software. The developers are
wxWidgets support is better than for much commercial software. The developers are
keen to fix bugs as soon as possible, though obviously there are no guarantees.
<P>
<H3><a name="users">Who uses wxWindows?</a></H3>
<H3><a name="users">Who uses wxWidgets?</a></H3>
Many organisations - commercial, government, and academic - across the
world. It&#39;s impossible to estimate the true number of users, since
wxWindows is obtained by many different means, and we cannot monitor
wxWidgets is obtained by many different means, and we cannot monitor
distribution. The mailing list contains around 300-400 entries which is
quite large for a list of this type.<P>
@@ -91,7 +91,7 @@ Our highest-profile user yet is industry veteran and Lotus Corp. founder Mitch K
and his <a href="http://www.osafoundation.org" target=_new>Open Source Applications Foundation</a>.
<P>
<H3><a name="platforms">What platforms are supported by wxWindows 2?</a></H3>
<H3><a name="platforms">What platforms are supported by wxWidgets 2?</a></H3>
<ul>
<li>Windows 3.1, Windows 95/98, Windows NT, Windows 2000, Windows ME.
@@ -99,20 +99,20 @@ and his <a href="http://www.osafoundation.org" target=_new>Open Source Applicati
<li>Unix with Motif or the free Motif clone Lesstif.
<li>Mac OS.
<li>Embedded platforms are being investigated. See the <a href="wxuniv.htm">wxUniversal</a> project.
<li>An OS/2 port is in progress, and you can also compile wxWindows for GTK+ or Motif
<li>An OS/2 port is in progress, and you can also compile wxWidgets for GTK+ or Motif
on OS/2.
</ul>
<P>
<H3><a name="specific">How does wxWindows 2 support platform-specific
<H3><a name="specific">How does wxWidgets 2 support platform-specific
features?</a></H3>
This is a hotly-debated topic amongst the developers. My own philosophy
is to make wxWindows as platform-independent as possible, but allow in a
is to make wxWidgets as platform-independent as possible, but allow in a
few classes (functions, window styles) that are platform-specific.
For example, Windows metafiles and Windows 95 taskbar icons have
their own classes on Windows, but nowhere else. Because these classes
are provided and are wxWindows-compatible, it doesn&#39;t take much
are provided and are wxWidgets-compatible, it doesn&#39;t take much
coding effort for an application programmer to add support for
some functionality that the user on a particular platform might otherwise
miss. Also, some classes that started off as platform-specific, such
@@ -120,29 +120,29 @@ as the MDI classes, have been emulated on other platforms. I can imagine
that even wxTaskBarIcon may be implemented for Unix desktops one day.
<P>
In other words, wxWindows is not a &#39;lowest common denominator&#39; approach,
In other words, wxWidgets is not a &#39;lowest common denominator&#39; approach,
but it will still be possible to write portable programs using the
core API. Forbidding some platform-specific classes would be a stupid
approach that would alienate many potential users, and encourage
the perception that toolkits such as wxWindows are not up to the demands
the perception that toolkits such as wxWidgets are not up to the demands
of today&#39;s sophisticated applications.<P>
Currently resources such as bitmaps and icons are handled in a platform-specific
way, but it is hoped to reduce this dependence in due course.<P>
Another reason why wxWindows 2 is not a &#39;lowest common denominator&#39; toolkit is that
Another reason why wxWidgets 2 is not a &#39;lowest common denominator&#39; toolkit is that
some functionality missing on some platform has been provided using generic,
platform-independent code, such as the wxTreeCtrl and wxListCtrl classes.<P>
<H3><a name="stl">Does wxWindows use STL? or the standard string class?</a></H3>
<H3><a name="stl">Does wxWidgets use STL? or the standard string class?</a></H3>
No. This is a much-discussed topic that has (many times) ended with the conclusion that it is in
wxWindows&#39; best interests to avoid use of templates. Not all compilers can handle
wxWidgets&#39; best interests to avoid use of templates. Not all compilers can handle
templates adequately so it would dramatically reduce the number of compilers
and platforms that could be supported. It would also be undersirable to make
wxWindows dependent on another large library that may have to be downloaded and installed.
wxWidgets dependent on another large library that may have to be downloaded and installed.
In addition, use of templates can lead to executable bloat, which is something
wxWindows 2 is strenously trying to avoid.<P>
wxWidgets 2 is strenously trying to avoid.<P>
The standard C++ string class is not used, again because it is not available to all compilers,
and it is not necessarily a very efficient implementation. Also, we retain more flexibility
@@ -150,7 +150,7 @@ by being able to modify our own string class. Some compatibility with the string
has been built into wxString.<P>
There is nothing to stop an application using templates or the string class for its own
purposes. With wxWindows debugging options on, you may find you get errors when including
purposes. With wxWidgets debugging options on, you may find you get errors when including
STL headers. You can work around it either by switching off memory checking,
or by adding this to a header before you include any STL files:<P>
@@ -163,41 +163,41 @@ or by adding this to a header before you include any STL files:<P>
<P>
<H3><a name="richedit">Is there a rich edit/markup widget for wxWindows 2?</a></H3>
<H3><a name="richedit">Is there a rich edit/markup widget for wxWidgets 2?</a></H3>
These are the possibilities so far:<P>
<ul>
<li>See <a href="http://www.scintilla.org" target=_top>www.scintilla.org</a> for
a very nice syntax-highlighting editor widget. Robin Dunn has written a wxWindows wrapper
for this widget, available in the wxWindows distribution under contrib/src/stc.
a very nice syntax-highlighting editor widget. Robin Dunn has written a wxWidgets wrapper
for this widget, available in the wxWidgets distribution under contrib/src/stc.
<li>If you only need to display marked-up information, rather than edit it,
then wxHTML will suit your needs. wxHTML is built into wxWindows - please see the reference
then wxHTML will suit your needs. wxHTML is built into wxWidgets - please see the reference
manual for details, and samples/html.
<li>There are rich edit widgets in both WIN32 and GTK+, but there is currently
no wxWindows wrapper for these (but text attribute functions are being added in the wxWindows 2.3.x series).
no wxWidgets wrapper for these (but text attribute functions are being added in the wxWidgets 2.3.x series).
</ul>
<P>
<h3><a name="exceptions">How to use C++ exceptions with wxWindows?</a></h3>
<h3><a name="exceptions">How to use C++ exceptions with wxWidgets?</a></h3>
wxWindows library itself is unfortunately <i>not</i> exception-safe (as its
wxWidgets library itself is unfortunately <i>not</i> exception-safe (as its
initial version predates, by far, the addition of the exceptions to the C++
language). However you can still use the exceptions in your own code and use
the other libraries using the exceptions for the error reporting together with
wxWindows.
wxWidgets.
<p>
There are a few issues to keep in mind, though:
<ul>
<li>You shouldn&#39;t let the exceptions propagate through wxWindows code,
<li>You shouldn&#39;t let the exceptions propagate through wxWidgets code,
in particular you should always catch the exceptions thrown by the
functions called from an event handler in the handler itself and not
let them propagate upwards to wxWindows.
let them propagate upwards to wxWidgets.
<li>You may need to ensure that the compiler support for the exceptions is
enabled as, considering that wxWindows itself doesn&#39;t use the
enabled as, considering that wxWidgets itself doesn&#39;t use the
exceptions and turning their support on results in the library size
augmentation of 10% to 20%, it is turned off by default for a few
compilers. Moreover, for gcc (or at least its mingw version) you must
@@ -208,18 +208,18 @@ There are a few issues to keep in mind, though:
<p>
<H3><a name="dev">How is wxWindows being developed?</a></H3>
<H3><a name="dev">How is wxWidgets being developed?</a></H3>
We are using the <a href="cvs.htm">CVS</a> system to develop and maintain wxWindows. This allows
We are using the <a href="cvs.htm">CVS</a> system to develop and maintain wxWidgets. This allows
us to make alterations and upload them instantly to the server, from
which others can update their source.<P>
To build source from CVS, see the file BuildCVS.txt in the top-level wxWindows distribution
To build source from CVS, see the file BuildCVS.txt in the top-level wxWidgets distribution
directory.<P>
<H3><a name="distrib">How is wxWindows distributed?</a></H3>
<H3><a name="distrib">How is wxWidgets distributed?</a></H3>
By ftp, and via the <a href="cdrom2.htm">wxWindows CD-ROM</a>.
By ftp, and via the <a href="cdrom2.htm">wxWidgets CD-ROM</a>.
<P>
If you are feeling adventurous, you may also check out the sources directly
from <a href="cvs.htm">cvs</a>.
@@ -227,40 +227,40 @@ from <a href="cvs.htm">cvs</a>.
<H3><a name="future">What are the plans for the future?</a></H3>
Currently we&#39;re working too hard on getting wxWindows finished (are GUI toolkits ever
finished?) to think very far ahead. However, we know we want to make wxWindows as robust
Currently we&#39;re working too hard on getting wxWidgets finished (are GUI toolkits ever
finished?) to think very far ahead. However, we know we want to make wxWidgets as robust
and well-publicised as possible. We also want to aim for better platform-independence of
resources such as icons and bitmaps, standardising on PNG and XPM for all platforms.<P>
Other possibilities include: DCOM/CORBA compatibility; a wxWindows book;
Other possibilities include: DCOM/CORBA compatibility; a wxWidgets book;
<a href="http://wxworkshop.sourceforge.net/">wxWorkshop</a>, an IDE;
other platforms, especially embedded systems; other interface abilities such as speech output.<P>
We will investigate the possibility of compiler or operating system vendors bundling wxWindows with
We will investigate the possibility of compiler or operating system vendors bundling wxWidgets with
their product.<P>
The high-level goal of wxWindows is to be thought of as the number one C++ framework,
The high-level goal of wxWidgets is to be thought of as the number one C++ framework,
for virtually any platform. Move over, MFC!<P>
<h3><a name="base">What is wxBase?</a></h3>
wxBase is a subset of wxWindows comprised by the non-GUI classes. It includes
wxWindows container and primitive data type classes (including wxString,
wxBase is a subset of wxWidgets comprised by the non-GUI classes. It includes
wxWidgets container and primitive data type classes (including wxString,
wxDateTime and so on) and also useful wrappers for the operating system objects
such as files, processes, threads, sockets and so on. With very minor
exceptions wxBase may be used in exactly the same way as wxWindows but it
exceptions wxBase may be used in exactly the same way as wxWidgets but it
doesn&#39;t require a GUI to run and so is ideal for creating console mode
utilities or server programs. It is also possible to create a program which can
be compiled either as a console application (using wxBase) or a GUI one (using
a full featured wxWindows port).
a full featured wxWidgets port).
<H3><a name="univ">What is wxUniversal?</a></H3>
The main difference between wxUniversal-based ports (such as wxX11, wxMGL) and other ports (such as wxMSW, wxGTK+, wxMac)
is that wxUniversal implements all controls (or widgets) in
wxWindows itself thus allowing to have much more flexibility (for example, support for
wxWidgets itself thus allowing to have much more flexibility (for example, support for
themes even under MS Windows). It also means that it is now much easier to
port wxWindows to a new platform as only the low-level classes must be ported
port wxWidgets to a new platform as only the low-level classes must be ported
which make for a small part of the library.
<p>
You may find more about wxUniversal <a href=wxuniv.htm>here</a>.
@@ -269,7 +269,7 @@ You may find more about wxUniversal <a href=wxuniv.htm>here</a>.
The Java honeymoon period is over :-) and people are realising that it cannot
meet all their cross-platform development needs. We don&#39;t anticipate a major threat
from Java, and the level of interest in wxWindows is as high as ever.<P>
from Java, and the level of interest in wxWidgets is as high as ever.<P>
<H3><a name="dotnet">What about .NET/Mono?</a></H3>
@@ -281,25 +281,27 @@ garbage collection and various other Java-like language features.<P>
Although this may be attractive to some developers, there
is a variety of reasons why the .NET/Mono combination is unlikely
to make wxWindows redundant. Please note that the following comments
to make wxWidgets redundant. Please note that the following comments
are Julian Smart's opinions.<P>
<ol>
<li>Not everyone wants or needs net services.
<li>C++ will be used for a long time to come; compared with C++, C&#35; is a recent development and its future is not certain.
<li>Mono Forms may only target Winelib (at least to begin with), so the end result is not as native as
wxWindows (I'm aware there is GTK&#35; for use with the C&#35; language).
wxWidgets (I'm aware there is GTK&#35; for use with the C&#35; language).
<li>C&#35; is usually byte-compiled and therefore slower. Plus, .NET adds a layer of overhead to the client computer
that wxWindows does not require.
<li>Mono hasn't proven its long-term viability yet (it's a complex system of components); wxWindows is ready now.
that wxWidgets does not require.
<li>Mono hasn't proven its long-term viability yet (it's a complex system of components); wxWidgets is ready now.
<li>You may not wish to buy into Microsoft marketing spin and APIs.
<li>Microsoft may at some point sue developers of non-Microsoft .NET implementations. After all,
platform-independence is not in Microsoft's interest.
<li>.NET might never be implemented on some platforms, especially Mac and embedded variants of Linux.
<li>wxPython and other language variants provide further reasons for wxWindows to continue.
<li>wxPython and other language variants provide further reasons for wxWidgets to continue.
<li>The same issue exists for Qt: if Qt sales remain strong, it's a good indication that
the market for a C++-based approach is still there. (Either that, or everyone's turning to wxWindows!)
the market for a C++-based approach is still there. (Either that, or everyone's turning to wxWidgets!)
</ol>
There is nothing to stop folk from developing a C&#35; version of the wxWindows API;
There is nothing to stop folk from developing a C&#35; version of the wxWidgets API;
we already have bindings to Python, Perl, JavaScript, Lua, Basic, and Eiffel.
Update: a <a href="http://wxnet.sourceforge.net/" target=_new>wx.NET</a> project is now in progress.

31
docs/html/faqgtk.htm
View File

@@ -2,7 +2,7 @@
<HTML>
<HEAD>
<TITLE>wxWindows 2 for GTK FAQ</TITLE>
<TITLE>wxWidgets 2 for GTK FAQ</TITLE>
</HEAD>
<BODY BGCOLOR=#FFFFFF TEXT=#000000 VLINK="#00376A" LINK="#00529C" ALINK="#313063">
@@ -13,7 +13,7 @@
<tr>
<td bgcolor="#004080" align=left height=24 background="images/bluetitlegradient.gif">
<font size=+1 face="Arial, Lucida Sans, Helvetica" color="#FFFFFF">
<b>wxWindows 2 for GTK FAQ</b>
<b>wxWidgets 2 for GTK FAQ</b>
</font>
</td>
</tr>
@@ -26,25 +26,26 @@ See also <a href="faq.htm">top-level FAQ page</a>.
<h3>List of questions in this category</h3>
<ul>
<li><a href="#wxgtk">What is wxWindows 2 for GTK+?</a></li>
<li><a href="#locale">Why doesn&#39;t reading floating point numbers work when using wxWindows?</a></li>
<li><a href="#wxgtk">What is wxWidgets 2 for GTK+?</a></li>
<li><a href="#locale">Why doesn&#39;t reading floating point numbers work when using wxWidgets?</a></li>
<li><a href="#gnome">Does wxGTK have GNOME support?</a></li>
<li><a href="#redhat">Warning about GTK libraries supplied with RedHat</a></li>
<li><a href="#bincompat">What range of Intel Linux platforms will a given application binary be usable on?</a></li>
<li><a href="#static">Can I statically link the GTK+ library?</a></li>
<li><a href="#charinframe">Why does my simple program using <tt>EVT_CHAR</tt> doesn't work?</a></li>
<li><a href="#charinframe">Why does my simple program using <tt>EVT_CHAR</tt> not work?</a></li>
<li><a href="#debugging">How do I trace the cause of an X11 error such as BadMatch?</a></li>
</ul>
<hr>
<h3><a name="wxgtk">What is wxWindows 2 for GTK?</a></h3>
<h3><a name="wxgtk">What is wxWidgets 2 for GTK?</a></h3>
wxWindows 2 for GTK is a port of wxWindows to the <a href="http://www.gimp.org/gtk" target=_top>GTK+ toolkit</a>,
which is freely available for most flavours of Unix with X. wxWindows 2 for GTK is
wxWidgets 2 for GTK is a port of wxWidgets to the <a href="http://www.gimp.org/gtk" target=_top>GTK+ toolkit</a>,
which is freely available for most flavours of Unix with X. wxWidgets 2 for GTK is
often abbreviated to wxGTK. wxGTK has a separate home page <a href="http://www.freiburg.linux.de/~wxxt" target=_top>here</a>.
<P>
<h3><a name="locale">Why doesn&#39;t reading floating point numbers work when using wxWindows?</a></h3>
<h3><a name="locale">Why doesn&#39;t reading floating point numbers work when using wxWidgets?</a></h3>
If your program reads the floating point numbers in the format <tt>123.45</tt>
from a file, it may suddently start returning just <tt>123</tt> instead of the
@@ -74,7 +75,7 @@ future, probably as a separate library.
<h3><a name="redhat">Warning about GTK+ libraries supplied with RedHat</a></h3>
It seems that some versions of RedHat include a badly patched version of GTK+ (not wxGTK)
which causes some trouble with wxWindows&#39; socket code. Common symptoms are that when
which causes some trouble with wxWidgets&#39; socket code. Common symptoms are that when
a client tries to establish a connection to an existing server which refuses the request,
the client will get notified twice, first getting a LOST event and then a CONNECT event.
This problem can be solved by updating GTK with an official distribution of the library.
@@ -99,7 +100,7 @@ No, this is not possible. It leads to crashes in GTK+.
<P>
<h3><a name="#charinframe">Why does my simple program using
<tt>EVT_CHAR</tt> doesn't work?</a></h3>
<tt>EVT_CHAR</tt> not work?</a></h3>
In wxGTK, the frames never get focus and so can never receive <tt>CHAR</tt>
nor <tt>KEY</tt> events so an <tt>EVT_CHAR</tt> handler for a frame will be
@@ -109,6 +110,14 @@ frame.
<p>
<h3><a name="#debugging">How do I trace the cause of an X11 error such as BadMatch?</h3>
When a fatal X11 error occurs, the application quits with no stack trace.
To find out where the problem is, put a breakpoint on g_log (<tt>b g_log</tt>
in gdb).
<p>
</font>
</BODY>

40
docs/html/faqmac.htm
View File

@@ -2,7 +2,7 @@
<HTML>
<HEAD>
<TITLE>wxWindows 2 for Mac FAQ</TITLE>
<TITLE>wxWidgets 2 for Mac FAQ</TITLE>
</HEAD>
<BODY BGCOLOR=#FFFFFF TEXT=#000000 VLINK="#00376A" LINK="#00529C" ALINK="#313063">
@@ -13,7 +13,7 @@
<tr>
<td bgcolor="#004080" align=left height=24 background="images/bluetitlegradient.gif">
<font size=+1 face="Arial, Lucida Sans, Helvetica" color="#FFFFFF">
<b>wxWindows 2 for Mac FAQ</b>
<b>wxWidgets 2 for Mac FAQ</b>
</font>
</td>
</tr>
@@ -38,7 +38,7 @@ See also <a href="faq.htm">top-level FAQ page</a>.
<li><a href="#smarterrors">What are the smart preprocessing errors with the Apple Developer Tools?</a></li>
<li><a href="#aboutmenu">How does wxMac support the standard Apple About menu item and Help menu?</a></li>
<li><a href="#findericon">How do I add an icon to my application?</a></li>
<li><a href="#switching">How can I easily switch between different versions of wxWindows in CodeWarrior?</a></li>
<li><a href="#switching">How can I easily switch between different versions of wxWidgets in CodeWarrior?</a></li>
</ul>
<hr>
@@ -54,15 +54,15 @@ The author of this port is <a href="mailto:csomor@advancedconcepts.ch">Stefan Cs
<h3><a name="macplat">Which Mac platforms are supported?</a></h3>
wxWindows 2 can be used to develop and deliver applications on Classic Mac OS (e.g. Mac OS 8.x/9.x) both as Carbon and non-Carbon applications.
wxWidgets 2 can be used to develop and deliver applications on Classic Mac OS (e.g. Mac OS 8.x/9.x) both as Carbon and non-Carbon applications.
<P>
A Mac OS X port is in progress in order to be able to build wxWindows applications using the Apple Developer Tools that are delivered with every copy of Mac OS X.
A Mac OS X port is in progress in order to be able to build wxWidgets applications using the Apple Developer Tools that are delivered with every copy of Mac OS X.
The Mac OS X port is based on and, for the most part, merged with the Carbon code for Classic Mac OS.
<P>
<h3><a name="macosx">How is the Mac OS X port different from the Classic Mac OS port?</a></h3>
wxMac for Mac OS X shares code both with wxMac for Mac OS and common Unix code in wxWindows. The aim is to use the same Mac OS Carbon code both for Classic Mac OS and for Mac OS X while leveraging the fact that Mac OS X is a BSD Unix.
wxMac for Mac OS X shares code both with wxMac for Mac OS and common Unix code in wxWidgets. The aim is to use the same Mac OS Carbon code both for Classic Mac OS and for Mac OS X while leveraging the fact that Mac OS X is a BSD Unix.
<P>
This hybrid approach was suggested by Apple to the <a href="http://www.mozilla.org/ports/fizzilla/">Fizzilla</a> team working on <a href="http://www.mozilla.org/">Mozilla</a> for Mac OS X.
<P>
@@ -87,7 +87,7 @@ Under Mac OS X, the Developer Tools are sufficient to build wxMac. CodeWarrior P
<h3><a name="filetypes">How does CVS handle file types/creators under Mac OS 8.x/9.x?</a></h3>
Before checking out the wxWindows code using a CVS client under Mac OS 8.x/9.x, be sure your computer is set up to treat <code>xpm</code> and <code>xbm</code> images correctly:
Before checking out the wxWidgets code using a CVS client under Mac OS 8.x/9.x, be sure your computer is set up to treat <code>xpm</code> and <code>xbm</code> images correctly:
<ul>
<li>bring up the Internet control panel, select the <i>Advanced Options</i> tab, click on the <i>File Mapping</i> icon from the list at the left and see if there are is an entry for ".xpm" files and another for ".xbm".
<li>if an entry exists, click <i>Change...</i> and make sure <i>File Type</i> is <code>TEXT</code> (just those four capital letters); correct it if necessary. If there is no entry, make one with type set to <code>TEXT</code> and creator set to anything you like; reasonable choices include <code>GKON</code> (Graphic Converter) or <code>CWIE</code> (CodeWarrior).
@@ -101,8 +101,8 @@ The Mac OS X CVS client does not handle file types and creators at all (just lik
<P>
All files checked out under Mac OS X will be untyped and CodeWarrior will not recognize them correctly. To correct this, use the autotyper provided in the CVS sources:
<ul>
<li>decode and decompress the file <code>wxWindows/docs/mac/TypeAsMetrowerksText.sea.hqx</code>
<li>drag the wxWindows CVS sandbox directory onto the autotyper and most of the files will be typed according to the file extension
<li>decode and decompress the file <code>wxWidgets/docs/mac/TypeAsMetrowerksText.sea.hqx</code>
<li>drag the wxWidgets CVS sandbox directory onto the autotyper and most of the files will be typed according to the file extension
</ul>
<P>
@@ -125,11 +125,11 @@ This is also necessary even if you don&#39;want to build the Carbon targets.
<P>
Build the projects (<code>makemac6.mcp</code> for CodeWarrior Pro 6; <code>makemac.mpc</code> for CodeWarrior Pro 5) in the following five directories:
<ul>
<li>wxWindows:src:
<li>wxWindows:src:jpeg:
<li>wxWindows:src:png:
<li>wxWindows:src:tiff:
<li>wxWindows:src:zlib:
<li>wxWidgets:src:
<li>wxWidgets:src:jpeg:
<li>wxWidgets:src:png:
<li>wxWidgets:src:tiff:
<li>wxWidgets:src:zlib:
</ul>
<P>
@@ -139,8 +139,8 @@ You need to have the Apple Developer Tools installed. The Developer Tools CD is
<P>
Building wxMac completely without configure is not supported.
<P>
Building wxWindows directly in the CVS sandbox is not recommended. Instead, wxWindows should be built in a directory configured relatively to the CVS sandbox.
For instance, to build wxMac with configure, start in the base wxWindows directory and type:
Building wxWidgets directly in the CVS sandbox is not recommended. Instead, wxWidgets should be built in a directory configured relatively to the CVS sandbox.
For instance, to build wxMac with configure, start in the base wxWidgets directory and type:
<ul>
<li><code>mkdir macbuild</code>
<li><code>cd macbuild</code>
@@ -197,12 +197,12 @@ This error can sometimes be corrected or avoided by modifying the source code. H
<h3><a name="aboutmenu">How does wxMac support the standard Apple About menu item and Help menu?</a></h3>
Because wxWindows does not have a specific API for the <i>About</i> menu item or the <i>Help</i> menu, the Mac OS port uses some static variables to help the engine make the right decisions:
Because wxWidgets does not have a specific API for the <i>About</i> menu item or the <i>Help</i> menu, the Mac OS port uses some static variables to help the engine make the right decisions:
<ul>
<li>It assumes that the <i>About</i> menu item is part of a <i>Help</i> menu.
<li>The title of the <i>Help</i> menu is stored in <code>wxApp::s_macHelpMenuTitleName</code>, it defaults to "&Help", but you can change it in your constructor to your specific menu title.
<li>The item Id of the <i>About</i> menu is stored in <code>wxApp::s_macAboutMenuItemID</code>, it defaults to <code>wxID_ABOUT</code>, but can be changed as well to suit your needs.
<li>The other items of the wxWindows help menu are appended to the Mac OS <i>Help</i> menu and the translation of Ids is handled transparently for your application.
<li>The other items of the wxWidgets help menu are appended to the Mac OS <i>Help</i> menu and the translation of Ids is handled transparently for your application.
</ul>
<P>
@@ -215,10 +215,10 @@ your project and in the CodeWarrior Settings add a check mark under Linker:Outpu
Flags/Finder Flags/Has Custom Icon.
<P>
<h3><a name="switching">How can I easily switch between different versions of wxWindows in CodeWarrior?</a></h3>
<h3><a name="switching">How can I easily switch between different versions of wxWidgets in CodeWarrior?</a></h3>
Sometimes you want to test your application against different versions
of wxWindows, for example a stable version of wxWindows versus a development version.
of wxWidgets, for example a stable version of wxWidgets versus a development version.
The easiest way to do this is to create a symbolic path.<P>
Under Edit-Preferences in General:Source Trees, type a name (for example WXWIN)

8
docs/html/faqmot.htm
View File

@@ -2,7 +2,7 @@
<HTML>
<HEAD>
<TITLE>wxWindows 2 for Motif FAQ</TITLE>
<TITLE>wxWidgets 2 for Motif FAQ</TITLE>
</HEAD>
<BODY BGCOLOR=#FFFFFF TEXT=#000000 VLINK="#00376A" LINK="#00529C" ALINK="#313063">
@@ -13,7 +13,7 @@
<tr>
<td bgcolor="#004080" align=left height=24 background="images/bluetitlegradient.gif">
<font size=+1 face="Arial, Lucida Sans, Helvetica" color="#FFFFFF">
<b>wxWindows 2 for Motif FAQ</b>
<b>wxWidgets 2 for Motif FAQ</b>
</font>
</td>
</tr>
@@ -27,7 +27,7 @@ See also <a href="faq.htm">top-level FAQ page</a>.
<ul>
<li><a href="#versiob">What version of Motif do I need?</a></li>
<li><a href="#missing">What features are missing or partially implemented?</a></li>
<li><a href="#dialoged">Does Dialog Editor work with wxWindows for Motif?</a></li>
<li><a href="#dialoged">Does Dialog Editor work with wxWidgets for Motif?</a></li>
<li><a href="#refresh">Why are windows are not refreshed properly until I resize them?</a></li>
</ul>
<hr>
@@ -62,7 +62,7 @@ system is in preparation.
<p>
<h3><a name="dialoged">Does Dialog Editor work with wxWindows for Motif?</a></h3>
<h3><a name="dialoged">Does Dialog Editor work with wxWidgets for Motif?</a></h3>
Suport for Dialog Editor is almost there, but there are some wrinkles to iron
out. You may find it&#39;s useful though: compile it and see.

128
docs/html/faqmsw.htm
View File

@@ -2,7 +2,7 @@
<HTML>
<HEAD>
<TITLE>wxWindows 2 for Windows FAQ</TITLE>
<TITLE>wxWidgets 2 for Windows FAQ</TITLE>
</HEAD>
<BODY BGCOLOR=#FFFFFF TEXT=#000000 VLINK="#00376A" LINK="#00529C" ALINK="#313063">
@@ -13,7 +13,7 @@
<tr>
<td bgcolor="#004080" align=left height=24 background="images/bluetitlegradient.gif">
<font size=+1 face="Arial, Lucida Sans, Helvetica" color="#FFFFFF">
<b>wxWindows 2 for Windows FAQ</b>
<b>wxWidgets 2 for Windows FAQ</b>
</font>
</td>
</tr>
@@ -29,18 +29,19 @@ See also <a href="faq.htm">top-level FAQ page</a>.
<li><a href="#wince">What about Windows CE?</a></li>
<li><a href="#winxp">What do I need to do for Windows XP?</a></li>
<li><a href="#compilers">What compilers are supported?</a></li>
<li><a href="#bestcompiler">Which is the best compiler to use with wxWindows 2?</a></li>
<li><a href="#bestcompiler">Which is the best compiler to use with wxWidgets 2?</a></li>
<li><a href="#unicode">Is Unicode supported?</a></li>
<li><a href="#doublebyte">Does wxWindows support double byte fonts (Chinese/Japanese/Korean etc.)?</a></li>
<li><a href="#dll">Can you compile wxWindows 2 as a DLL?</a></li>
<li><a href="#doublebyte">Does wxWidgets support double byte fonts (Chinese/Japanese/Korean etc.)?</a></li>
<li><a href="#dll">Can you compile wxWidgets 2 as a DLL?</a></li>
<li><a href="#exesize">How can I reduce executable size?</a></li>
<li><a href="#mfc">Is wxWindows compatible with MFC?</a></li>
<li><a href="#mfc">Is wxWidgets compatible with MFC?</a></li>
<li><a href="#setuph">Why do I get errors about setup.h not being found?</a></li>
<li><a href="#asuffix">Why do I get errors about FooBarA when I only use FooBar in my program?</a></li>
<li><a href="#newerrors">Why my code fails to compile with strange errors about new operator?</a></li>
<li><a href="#mfcport">How do I port MFC applications to wxWindows?</a></li>
<li><a href="#mfcport">How do I port MFC applications to wxWidgets?</a></li>
<li><a href="#crash">Why do I sometimes get bizarre crash problems using VC++ 5/6?</a></li>
<li><a href="#makefiles">How are the wxWindows makefiles edited under Windows?</a></li>
<li><a href="#vcdebug">How do you use VC++&#39;s memory leak checking instead of that in wxWindows?</a></li>
<li><a href="#makefiles">How are the wxWidgets makefiles edited under Windows?</a></li>
<li><a href="#vcdebug">How do you use VC++&#39;s memory leak checking instead of that in wxWidgets?</a></li>
<li><a href="#shortcutproblem">Why are menu hotkeys or shortcuts not working in my application?</a></li>
<li><a href="#regconfig">Why can I not write to the HKLM part of the registry with wxRegConfig?</a></li>
<li><a href="#access">Is MS Active Accessibility supported?</a></li>
@@ -49,11 +50,11 @@ See also <a href="faq.htm">top-level FAQ page</a>.
<h3><a name="platforms">Which Windows platforms are supported?</a></h3>
wxWindows 2 can be used to develop and deliver applications on Windows 3.1, Win32s,
wxWidgets 2 can be used to develop and deliver applications on Windows 3.1, Win32s,
Windows 95, Windows 98, Windows NT, Windows 2000, and Windows XP. A Windows CE
version is being looked into (see below).<P>
wxWindows 2 is designed to make use of WIN32 features and controls. However, unlike Microsoft,
wxWidgets 2 is designed to make use of WIN32 features and controls. However, unlike Microsoft,
we have not forgotten users of 16-bit Windows. Most features
work under Windows 3.1, including wxTreeCtrl and wxListCtrl using the generic implementation.
However, don&#39;t expect very Windows-95-specific classes to work, such as wxTaskBarIcon. The wxRegConfig
@@ -63,23 +64,23 @@ makefiles to see what other files have been left out.
16-bit compilation is supported under Visual C++ 1.5, and Borland BC++ 4 to 5.
<P>
wxWindows 2 for Windows will also compile on Unix with gcc using Wine from <a href="http://www.winehq.org" target=_top>WineHQ</a>.
wxWidgets 2 for Windows will also compile on Unix with gcc using Wine from <a href="http://www.winehq.org" target=_top>WineHQ</a>.
The resulting executables are Unix binaries that work with the Wine Windows API emulator.<P>
You can also compile wxWindows 2 for Windows on Unix with Cygwin or Mingw32, resulting
You can also compile wxWidgets 2 for Windows on Unix with Cygwin or Mingw32, resulting
in executables that will run on Windows. So in theory you could write your applications
using wxGTK or wxMotif, then check/debug your wxWindows for Windows
using wxGTK or wxMotif, then check/debug your wxWidgets for Windows
programs with Wine, and finally produce an ix86 Windows executable using Cygwin/Mingw32,
without ever needing a copy of Microsoft Windows. See the Technical Note on the Web site detailing cross-compilation.<P>
<h3><a name="wince">What about Windows CE?</a></h3>
This is under consideration, though we need to get wxWindows Unicode-aware first.
This is under consideration, though we need to get wxWidgets Unicode-aware first.
There are other interesting issues, such as how to combine the menubar and toolbar APIs
as Windows CE requires. But there&#39;s no doubt that it will be possible, albeit
by mostly cutting down wxWindows 2 API functionality, and adding a few classes here
and there. Since wxWindows for 2 produces small binaries (less than 300K for
the statically-linked &#39;minimal&#39; sample), shoehorning wxWindows 2 into a Windows CE device&#39;s limited
by mostly cutting down wxWidgets 2 API functionality, and adding a few classes here
and there. Since wxWidgets for 2 produces small binaries (less than 300K for
the statically-linked &#39;minimal&#39; sample), shoehorning wxWidgets 2 into a Windows CE device&#39;s limited
storage should not be a problem.<P>
<h3><a name="winxp">What do I need to do for Windows XP?</a></h3>
@@ -121,7 +122,7 @@ line:<P>
1 24 "winxp.manifest"
</PRE>
In wxWindows 2.5, this will be in the wx/msw/wx.rc and
In wxWidgets 2.5, this will be in the wx/msw/wx.rc and
so will happen automatically so long as you include wx.rc
in your own .rc file.<P>
@@ -132,7 +133,7 @@ article</a>.
<h3><a name="compilers">What compilers are supported?</a></h3>
Please see the wxWindows 2 for Windows install.txt file for up-to-date information, but
Please see the wxWidgets 2 for Windows install.txt file for up-to-date information, but
currently the following are known to work:<P>
<ul>
@@ -149,18 +150,18 @@ currently the following are known to work:<P>
There is a linking problem with Symantec C++ which I hope someone can help solve.
<P>
<h3><a name="bestcompiler">Which is the best compiler to use with wxWindows 2?</a></h3>
<h3><a name="bestcompiler">Which is the best compiler to use with wxWidgets 2?</a></h3>
It&#39;s partly a matter of taste, but I (JACS) prefer Visual C++ since the debugger is very
good, it&#39;s very stable, the documentation is extensive, and it generates small executables.
Since project files are plain text, it&#39;s easy for me to generate appropriate project files
for wxWindows samples.<P>
for wxWidgets samples.<P>
Borland C++ is fine - and very fast - but it&#39;s hard (impossible?) to use the debugger without using project files, and
the debugger is nowhere near up to VC++&#39;s quality. The IDE isn&#39;t great.<P>
C++Builder&#39;s power isn&#39;t really used with wxWindows since it needs integration with its
own class library (VCL). For wxWindows, I&#39;ve only used it with makefiles, in which case
C++Builder&#39;s power isn&#39;t really used with wxWidgets since it needs integration with its
own class library (VCL). For wxWidgets, I&#39;ve only used it with makefiles, in which case
it&#39;s almost identical to BC++ 5.0 (the same makefiles can be used).<P>
You can&#39;t beat Cygwin&#39;s price (free), and you can debug adequately using gdb. However, it&#39;s
@@ -173,45 +174,45 @@ Watcom C++ is a little slow and the debugger is not really up to today&#39;s sta
Among the free compilers the best choice seem to be Borland C++ command line
tools and mingw32 (port of gcc to Win32). Both of them are supported by
wxWindows.
wxWidgets.
<h3><a name="unicode">Is Unicode supported?</a></h3>
Yes, Unicode is fully supported under Windows NT/2000 (Windows 9x don&#39;t
have Unicode support anyhow).
<h3><a name="doublebyte">Does wxWindows support double byte fonts (Chinese/Japanese/Korean etc.)?</a></h3>
<h3><a name="doublebyte">Does wxWidgets support double byte fonts (Chinese/Japanese/Korean etc.)?</a></h3>
An answer from <a href="mailto:goedde@logosoft.de">Klaus Goedde</a>:<p>
"For Japanese under Win2000, it seems that wxWindows has no problems to work with double byte char sets
"For Japanese under Win2000, it seems that wxWidgets has no problems to work with double byte char sets
(I mean DBCS, that&#39;s not Unicode). First you have to install Japanese support on your Win2K system
and choose for ANSI translation
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Nls\CodePage=932 (default is 1252 for Western).
Then you can see all the funny Japanese letters under wxWindows too.<P>
Then you can see all the funny Japanese letters under wxWidgets too.<P>
In a wxTextCtrl control you have to set the window style "wxTE_RICH", otherwise this control shows the wrong
letters.
I don&#39;t now whether it works on non W2K systems, because I&#39;m just starting using wxWindows."
I don&#39;t now whether it works on non W2K systems, because I&#39;m just starting using wxWidgets."
<P>
<h3><a name="dll">Can you compile wxWindows 2 as a DLL?</a></h3>
<h3><a name="dll">Can you compile wxWidgets 2 as a DLL?</a></h3>
Yes (using the Visual C++ or Borland C++ makefile), but be aware that distributing DLLs is a thorny issue
and you may be better off compiling statically-linked applications, unless you&#39;re
delivering a suite of separate programs, or you&#39;re compiling a lot of wxWindows applications
delivering a suite of separate programs, or you&#39;re compiling a lot of wxWidgets applications
and have limited hard disk space.<P>
With a DLL approach, and with different versions and configurations of wxWindows
With a DLL approach, and with different versions and configurations of wxWidgets
needing to be catered for, the end user may end up with a host of large DLLs in his or her Windows system directory,
negating the point of using DLLs. Of course, this is not a problem just associated with
wxWindows!
wxWidgets!
<P>
<h3><a name="exesize">How can I reduce executable size?</a></h3>
You can compile wxWindows as a DLL (see above, VC++/BC++ only at present). You should also
You can compile wxWidgets as a DLL (see above, VC++/BC++ only at present). You should also
compile your programs for release using non-debugging and space-optimisation options, but
take with VC++ 5/6 space optimisation: it can sometimes cause problems.<P>
@@ -224,24 +225,39 @@ use DLLs. Another good compression tool (probably better than Petite) is <a href
Please do not be surprised if MinGW produces a statically-linked minimal executable of 1 MB. Firstly, gcc
produces larger executables than some compilers. Secondly, this figure will
include most of the overhead of wxWindows, so as your application becomes more
include most of the overhead of wxWidgets, so as your application becomes more
complex, the overhead becomes proportionally less significant. And thirdly, trading executable compactness
for the enormous increase in productivity you get with wxWindows is almost always well worth it.<P>
for the enormous increase in productivity you get with wxWidgets is almost always well worth it.<P>
If you have a really large executable compiled with MinGW (for example 20MB) then
you need to configure wxWindows to compile without debugging information: see
you need to configure wxWidgets to compile without debugging information: see
docs/msw/install.txt for details. You may find that using configure instead
of makefile.g95 is easier, particularly since you can maintain debug and
release versions of the library simultaneously, in different directories.
Also, run 'strip' after linking to remove all traces of debug info.
<P>
<H3><a name="mfc">Is wxWindows compatible with MFC?</a></H3>
<H3><a name="mfc">Is wxWidgets compatible with MFC?</a></H3>
There is a sample which demonstrates MFC and wxWindows code co-existing in the same
application. However, don&#39;t expect to be able to enable wxWindows windows with OLE-2
There is a sample which demonstrates MFC and wxWidgets code co-existing in the same
application. However, don&#39;t expect to be able to enable wxWidgets windows with OLE-2
functionality using MFC.<P>
<H3><a name="setuph">Why do I get errors about setup.h not being found?</a></H3>
When you build the wxWidgets library, setup.h is copied
from include/wx/msw/setup.h to e.g. lib/mswd/wx/setup.h (the path
depends on the configuration you're building). So you need to add
this include path if building using the static Debug library:<P>
lib/mswd<P>
or if building the static Release library, lib/msw.<P>
See also the <a href="http://wiki.wxwindows.org/wiki.pl?Table_Of_Contents">wxWiki Contents</a>
for more information.<P>
<H3><a name="asuffix">Why do I get errors about FooBarA when I only use FooBar in my program?</H3>
If you get errors like
@@ -271,16 +287,16 @@ The most common cause of this problem is the memory debugging settings in
setting <tt>wxUSE_GLOBAL_MEMORY_OPERATORS</tt> and
<tt>wxUSE_DEBUG_NEW_ALWAYS</tt> to 0 in this file
<li> Or leave them on but do <tt>#undef new</tt> after including any
wxWindows headers, like this the memory debugging will be still on
for wxWindows sources but off for your own code
wxWidgets headers, like this the memory debugging will be still on
for wxWidgets sources but off for your own code
</ul>
Notice that IMHO the first solution is preferable for VC++ users who can use
the <a href="#vcdebug">VC++ CRT memory debugging features</a> instead.
<H3><a name="mfcport">How do I port MFC applications to wxWindows?</a></H3>
<H3><a name="mfcport">How do I port MFC applications to wxWidgets?</a></H3>
Set up your interface from scratch using wxWindows (especially <a href="http://www.robeling.de" target=_top>wxDesigner</a>
Set up your interface from scratch using wxWidgets (especially <a href="http://www.robeling.de" target=_top>wxDesigner</a>
or <a href="http://www.anthemion.co.uk/dialogblocks/" target=_new>DialogBlocks</a> --
it&#39;ll save you a <i>lot</i> of time) and when you have a shell prepared, you can start
&#39;pouring in&#39; code from the MFC app, with appropriate
@@ -288,14 +304,14 @@ modifications. This is the approach I have used, and I found
it very satisfactory. A two-step process then - reproduce the bare
interface first, then wire it up afterwards. That way you deal
with each area of complexity separately. Don&#39;t try to think MFC
and wxWindows simultaneously from the beginning - it is easier to
and wxWidgets simultaneously from the beginning - it is easier to
reproduce the initial UI by looking at the behaviour of the MFC
app, not its code.
<H3><a name="crash">Why do I sometimes get bizarre crash problems using VC++ 5/6?</a></H3>
Some crash problems can be due to inconsistent compiler
options (and of course this isn&#39;t limited to wxWindows).
options (and of course this isn&#39;t limited to wxWidgets).
If strange/weird/impossible things start to happen please
check (dumping IDE project file as makefile and doing text comparison
if necessary) that the project settings, especially the list of defined
@@ -308,13 +324,13 @@ Editor, in Release mode with optimizations on. If in doubt,
switch off optimisations, although this will result in much
larger executables. It seems possible that the library can be created with
strong optimization, so long as the application is not strongly
optimized. For example, in wxWindows project, set to &#39;Minimum
optimized. For example, in wxWidgets project, set to &#39;Minimum
Size&#39;. In Dialog Editor project, set to &#39;Customize: Favor Small
Code&#39; (and no others). This will then work.<P>
<H3><a name="makefiles">How are the wxWindows makefiles edited under Windows?</a></H3>
<H3><a name="makefiles">How are the wxWidgets makefiles edited under Windows?</a></H3>
As of wxWindows 2.1, there is a new system written by Vadim Zeitlin, that
As of wxWidgets 2.1, there is a new system written by Vadim Zeitlin, that
generates the makefiles from templates using tmake.<P>
Here are Vadim&#39;s notes:<P>
@@ -360,7 +376,7 @@ files to be compiled. Some of them are only compiled in 16/32 bit mode.
Some other are only compiled with some compilers (others can&#39;t compile
them) - all this info is contained in this file.<P>
So now adding a new file to wxWindows is as easy as modifying filelist.txt
So now adding a new file to wxWidgets is as easy as modifying filelist.txt
(and Makefile.ams for Unix ports) and regenerating the makefiles - no
need to modify all files manually any more.<P>
@@ -370,11 +386,11 @@ I don&#39;t need it and can&#39;t test it, but it should be trivial to create
one from vc6.t - probably the only things to change would be the
version number in the very beginning and the /Z option - VC5 doesn&#39;t
support edit-and=continue). This is not an officially supported way
of building wxWindows (that is, nobody guarantees that it will work),
of building wxWidgets (that is, nobody guarantees that it will work),
but it has been very useful to me and I hope it will be also for
others. To generate wxWindows.dsp run<P>
others. To generate wxWidgets.dsp run<P>
<pre>tmake -t vc6 wxwin.pro -o ../../wxWindows.dsp</pre><P>
<pre>tmake -t vc6 wxwin.pro -o ../../wxWidgets.dsp</pre><P>
Then just include this project in any workspace or open it from VC IDE
and it will create a new workspace for you.<P>
@@ -388,13 +404,13 @@ directory by 10 (and the number of files to be maintained too).
<P>
<H3><a name="vcdebug">How do you use VC++&#39;s memory leak checking instead of that in wxWindows?</a></H3>
<H3><a name="vcdebug">How do you use VC++&#39;s memory leak checking instead of that in wxWidgets?</a></H3>
Vadim Zeitlin:
<pre>
On the VC++ level, it&#39;s just the matter of calling _CrtSetDbgFlag() in the very
beginning of the program. In wxWindows, this is done automatically when
beginning of the program. In wxWidgets, this is done automatically when
compiling with VC++ in debug mode unless wxUSE_GLOBAL_MEMORY_OPERATORS or
__NO_VC_CRTDBG__ are defined - this check is done in wx/msw/msvcrt.h which
is included from app.cpp which then calls wxCrtSetDbgFlag() without any
@@ -431,7 +447,7 @@ Currently this is not possible because the wxConfig family of classes is
supposed to deal with per-user application configuration data, and HKLM is
only supposed to be writeable by a user with Administrator privileges. In theory,
only installers should write to HKLM. This is still a point debated by the
wxWindows developers. There are at least two ways to work around it if you really
wxWidgets developers. There are at least two ways to work around it if you really
need to write to HKLM.<P>
First, you can use wxRegKey directly, for example:

4
docs/html/faqx11.htm
View File

@@ -2,7 +2,7 @@
<HTML>
<HEAD>
<TITLE>wxWindows 2 for X11 FAQ</TITLE>
<TITLE>wxWidgets 2 for X11 FAQ</TITLE>
</HEAD>
<BODY BGCOLOR=#FFFFFF TEXT=#000000 VLINK="#00376A" LINK="#00529C" ALINK="#313063">
@@ -13,7 +13,7 @@
<tr>
<td bgcolor="#004080" align=left height=24 background="images/bluetitlegradient.gif">
<font size=+1 face="Arial, Lucida Sans, Helvetica" color="#FFFFFF">
<b>wxWindows 2 for X11 FAQ</b>
<b>wxWidgets 2 for X11 FAQ</b>
</font>
</td>
</tr>

28
docs/html/i18n.htm
View File

@@ -2,7 +2,7 @@
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<meta name="Author" content="Vadim Zeitlin">
<title>List of translators for wxWindows</title>
<title>List of translators for wxWidgets</title>
</head>
<body>
@@ -10,7 +10,7 @@
<tr>
<td bgcolor="#004080" align=left height=24 background="images/bluetitlegradient.gif">
<font size=+1 face="Arial, Lucida Sans, Helvetica" color="#FFFFFF">
<b>wxWindows internationalization</b>
<b>wxWidgets internationalization</b>
</font>
</td>
</tr>
@@ -23,9 +23,9 @@
</center>
<p>
wxWindows uses a certain number of user-readable strings such as
wxWidgets uses a certain number of user-readable strings such as
<tt>"help"</tt> or <tt>"Load file"</tt> which should be translated to the
users language if it is different from English. wxWindows has built in support
users language if it is different from English. wxWidgets has built in support
for internationalization (i18n from now on) which allows for this to happen
automatically if the translations to the current language are available.
@@ -33,7 +33,7 @@ automatically if the translations to the current language are available.
You may find here the list of all existing translations with the addresses of
the official translators whom you should contact if you would like to submit
any corrections to the translations for your language. Also, please
<a href="#howtohelp">see below</a> if you would like to translate wxWindows to
<a href="#howtohelp">see below</a> if you would like to translate wxWidgets to
your language if it is not mentioned here (or to help with one which already
is -- it is quite helpful to have several translators for one language at
least for proof reading).
@@ -45,16 +45,16 @@ least for proof reading).
<hr>
<p>
Below is the table containing the list of languages supported by wxWindows.
Below is the table containing the list of languages supported by wxWidgets.
The columns of this table have the obvious meaning: in each row you will see
the language, the official translator (if any) for it and the status of the
translations as of wxWindows 2.3.
translations as of wxWidgets 2.3.
<p>
<table width=100% border=4 cellpadding=5 cellspacing=0>
<tr>
<td bgcolor="#004080" colspan=3> <font size=+1 face="Arial, Lucida Sans, Helvetica" color="#FFFFFF"> Languages supported in wxWindows 2.x </font> </td>
<td bgcolor="#004080" colspan=3> <font size=+1 face="Arial, Lucida Sans, Helvetica" color="#FFFFFF"> Languages supported in wxWidgets 2.x </font> </td>
</tr>
<tr>
@@ -236,16 +236,16 @@ translations as of wxWindows 2.3.
<hr>
<p>
wxWindows uses the standard GNU gettext tools for i18n so if you are already
familiar with them you shouldn&#39;t have any problems with working on wxWindows
wxWidgets uses the standard GNU gettext tools for i18n so if you are already
familiar with them you shouldn&#39;t have any problems with working on wxWidgets
translations. Here are the the steps you should follow:
<ol>
<li>Get the latest version of the file <tt>locale/wxstd.po</tt> from the
wxWindows source tree: if you&#39;re using <a href="cvs.htm">cvs</a>
wxWidgets source tree: if you&#39;re using <a href="cvs.htm">cvs</a>
or the <a href="http://wxwindows.sf.net/snapshots/">daily snapshots</a>,
you should already have it. Otherwise you can always
retrieve it directly from the cvs repository via the Web interface
<a href="http://cvs.wxwindows.org/viewcvs.cgi/wxWindows/locale/wxstd.po">here</a>.
<a href="http://cvs.wxwindows.org/viewcvs.cgi/wxWidgets/locale/wxstd.po">here</a>.
<li>Rename it to <tt>XY.po</tt> where <tt>"XY"</tt> is the 2 letter
<a href="http://lcweb.loc.gov/standards/iso639-2/englangn.html">ISO 639-1 language code</a>
@@ -264,13 +264,13 @@ translations. Here are the the steps you should follow:
<li>Send the finished translation to
<a href="mailto:vadim@wxwindows.org">Vadim Zeitlin</a> and it will be
added to the next wxWindows release or snapshot.
added to the next wxWidgets release or snapshot.
</ol>
<p>
In addition, please consider subscribing to the very low volume
<a href="http://lists.wxwindows.org/mailman/listinfo/wx-translators">
wxWindows translators</a> mailing list on which the news especially important
wxWidgets translators</a> mailing list on which the news especially important
for the translators are announced.
<p>

62
docs/html/index.htm
View File

@@ -1,7 +1,7 @@
<HTML>
<HEAD>
<TITLE>wxWindows Documentation</TITLE>
<TITLE>wxWidgets Documentation</TITLE>
</HEAD>
@@ -13,11 +13,11 @@
<IMG src="logo.gif" align=right hspace=10 vspace=0>
<b>Welcome to wxWindows 2, the premi&egrave;re cross-platform GUI C++ framework.</b><P>
<b>Welcome to wxWidgets 2, the premi&egrave;re cross-platform GUI C++ framework.</b><P>
This is an index of
the plain text, HTML, Windows Help and Acrobat documentation: availability depends on what you've
downloaded from the <a href="http://www.wxwindows.org">wxWindows Web site</a>.<br clear=all><P>
downloaded from the <a href="http://www.wxwindows.org">wxWidgets Web site</a>.<br clear=all><P>
<CENTER>
<FONT size=-1>
@@ -44,8 +44,8 @@ downloaded from the <a href="http://www.wxwindows.org">wxWindows Web site</a>.<b
<P>
Unless you installed a binary version of wxWindows using RPMs,
you will probably have to compile the wxWindows library first.
Unless you installed a binary version of wxWidgets using RPMs,
you will probably have to compile the wxWidgets library first.
Please read the platform-specific readme.txt and install.txt
for how to do this.
@@ -77,18 +77,18 @@ for how to do this.
<li><a href="faq.htm"><B>FAQ</B></a>:
<ul>
<li><a href="faqgen.htm">General questions</a>
<li><a href="faqgtk.htm">wxWindows 2 for GTK+</a>
<li><a href="faqmsw.htm">wxWindows 2 for Windows</a>
<li><a href="faqmot.htm">wxWindows 2 for Motif</a>
<li><a href="faqx11.htm">wxWindows 2 for X11</a>
<li><a href="faqmac.htm">wxWindows 2 for Mac</a>
<li><a href="faqgtk.htm">wxWidgets 2 for GTK+</a>
<li><a href="faqmsw.htm">wxWidgets 2 for Windows</a>
<li><a href="faqmot.htm">wxWidgets 2 for Motif</a>
<li><a href="faqx11.htm">wxWidgets 2 for X11</a>
<li><a href="faqmac.htm">wxWidgets 2 for Mac</a>
</ul>
<li>ToDo: <a href="../todo.txt"><b>General ToDo</b></a>,
<a href="../gtk/todo.txt">wxGTK</a>,
<a href="../motif/todo.txt">wxMotif</a>,
<a href="../msw/todo.txt">wxMSW</a>,
<a href="../mac/todo.txt">wxMac</a>
<li>List of <a href="../symbols.txt">preprocessor symbols</a> used in wxWindows
<li>List of <a href="../symbols.txt">preprocessor symbols</a> used in wxWidgets
</ul>
Further platform-specific notes:
@@ -103,7 +103,7 @@ Further platform-specific notes:
<tr>
<td bgcolor="#004080" align=left height=24 background="images/bluetitlegradient.gif">
<font size=+1 face="Arial, Lucida Sans, Helvetica" color="#FFFFFF">
<b><a name="manuals">wxWindows manuals</a></b>
<b><a name="manuals">wxWidgets manuals</a></b>
</font>
</td>
</tr>
@@ -115,7 +115,7 @@ To use manuals in wxHTML Help form (extension htb), you can use the <b>HelpView<
application, either compiling it from utils/helpview in the distribution,
or downloading a binary, for example from <a href="http://www.storylinescentral.com/helpview.htm">here</a>.<P>
See also the <a href="../pdf/wxTutorial.pdf">wxWindows Tutorial</a>
See also the <a href="../pdf/wxTutorial.pdf">wxWidgets Tutorial</a>
by Franky Braem, in PDF format.<P>
<P>
@@ -142,23 +142,23 @@ by Franky Braem, in PDF format.<P>
<tr>
<td align=center>
<a href="wx/wx.htm">wxWindows Reference</a>
<a href="wx/wx.htm">wxWidgets Reference</a>
</td>
<td align=center>
<a href="../winhelp/wx.hlp">wxWindows Reference</a>
<a href="../winhelp/wx.hlp">wxWidgets Reference</a>
</td>
<td align=center>
<a href="../htmlhelp/wx.chm">wxWindows Reference</a>
<a href="../htmlhelp/wx.chm">wxWidgets Reference</a>
</td>
<td align=center>
<a href="../htb/wx.htb">wxWindows Reference</a>
<a href="../htb/wx.htb">wxWidgets Reference</a>
</td>
<td align=center>
<a href="../pdf/wx.pdf">wxWindows Reference</a>
<a href="../pdf/wx.pdf">wxWidgets Reference</a>
</td>
</tr>
@@ -272,7 +272,7 @@ by Franky Braem, in PDF format.<P>
<li><a href="../tech/index.txt">Index of technical notes</a>
<li><a href="../tech/">Technical notes</a>
<li><a href="platform.htm">Platforms supported</a>
<li><a href="i18n.htm">Languages supported by wxWindows</a>
<li><a href="i18n.htm">Languages supported by wxWidgets</a>
</ul>
<P>
@@ -307,11 +307,11 @@ by Franky Braem, in PDF format.<P>
<P>
Each of the following samples demonstrates one or more aspect of wxWindows.<P>
Each of the following samples demonstrates one or more aspect of wxWidgets.<P>
<ul>
<li><a href="../../samples/calendar">artprov</a>: shows how you can customize the look of standard
wxWindows dialogs by replacing default bitmaps/icons with your own versions.
wxWidgets dialogs by replacing default bitmaps/icons with your own versions.
<li><a href="../../samples/calendar">calendar</a>: a sample to test the wxCalendarCtrl class.
<li><a href="../../samples/caret">caret</a>: a sample to test the wxCaret class.
<li><a href="../../samples/checklst">checklst</a>: demonstrates wxCheckListBox on
@@ -319,7 +319,7 @@ supported platforms (currently Windows and GTK only).
<li><a href="../../samples/config">config</a>: demonstrates use of wxConfig, which
defaults to wxRegConfig on WIN32, wxIniConfig on WIN16, and wxFileConfig on other platforms.
<li><a href="../../samples/console">console</a>: demonstrates a console application using
console-mode (no-GUI) compilation of wxWindows.
console-mode (no-GUI) compilation of wxWidgets.
<li><a href="../../samples/controls">controls</a>: sample showing a variety of controls, including
wxNotebook.
<li><a href="../../samples/db">db</a>: wxDB ODBC sample.
@@ -343,7 +343,7 @@ dynamically.
<li><a href="../../samples/exec">exec</a>: demonstrates wxExecute.
<li><a href="../../samples/font">font</a>: tests fonts, font enumerator, font encodings.
<li><a href="../../samples/grid">grid</a>: demonstrates the wxGrid class. This demo should work
when the old grid implementation is compiled into wxWindows, and also with the new implementation.
when the old grid implementation is compiled into wxWidgets, and also with the new implementation.
Please see newgrid below for a full demo of the new implementation's capabilities.
<li><a href="../../samples/help">help</a>: shows how to use wxHelpController.
<li><a href="../../samples/html">html</a>: a number of demos for the wxHTML class library, used inside
@@ -359,7 +359,7 @@ applications and also as a help facility.
<li><a href="../../samples/html/zip">zip</a>: shows how help files can be packaged in zip archives.
</ul>
<li><a href="../../samples/image">image</a>: shows off the cross-platform wxImage class.
<li><a href="../../samples/internat">internat</a>: use of wxWindows' internationalization support.
<li><a href="../../samples/internat">internat</a>: use of wxWidgets' internationalization support.
<li><a href="../../samples/joytest">joytest</a>: tests the wxJoystick class (currently Windows and GTK only).
<li><a href="../../samples/keyboard">keyboard</a>: tests keyboard support.
<li><a href="../../samples/layout">layout</a>: shows the constraint layout system in action.
@@ -370,15 +370,15 @@ WIN32, and using a generic version on other platforms).
scheme is used whereby child windows have full sizing and moving rights within the main
window. On other platforms, tabbed windows are used, where the children are always maximized.
<li><a href="../../samples/memcheck">memcheck</a>: demonstrates the memory checking/debugging facilities.
<li><a href="../../samples/mfc">mfc</a>: shows how to use MFC and wxWindows code in the same application (Windows only).
To compile this, you must edit include/wx/wxprec.h, comment out the windows.h inclusion, and recompile wxWindows.
<li><a href="../../samples/mfc">mfc</a>: shows how to use MFC and wxWidgets code in the same application (Windows only).
To compile this, you must edit include/wx/wxprec.h, comment out the windows.h inclusion, and recompile wxWidgets.
<li><a href="../../samples/minifram">minifram</a>: demonstrates a frame with a small title bar. On
platforms that don't support it, a normal-sized title bar is displayed.
<li><a href="../../samples/minimal">minimal</a>: just shows a frame, a menubar, and a statusbar. About as
small a wxWindows application as you can get.
small a wxWidgets application as you can get.
<li><a href="../../samples/mobile">mobile</a>: mini applications for embedded platforms.
<li><a href="../../samples/nativdlg">nativdlg</a>: shows how wxWindows can load a standard Windows
dialog resource, translating the controls into wxWindows controls (Windows only).
<li><a href="../../samples/nativdlg">nativdlg</a>: shows how wxWidgets can load a standard Windows
dialog resource, translating the controls into wxWidgets controls (Windows only).
<li><a href="../../samples/newgrid">newgrid</a>: demonstrates the new wxGrid implementation, by Michael Bedward and others.
<li><a href="../../samples/notebook">notebook</a>: shows the wxNotebook (tabbed window) control.
<li><a href="../../samples/oleauto">oleauto</a>: a little OLE automation controller (Windows only; requires
@@ -389,7 +389,7 @@ Excel to be present).
<li><a href="../../samples/proplist">proplist</a>: demonstrates the property list classes (a VB-style property editor).
<li><a href="../../samples/propsize">propsize</a>: demonstrates proportional sizer classes.
<li><a href="../../samples/regtest">regtest</a>: tests the low-level Windows registry functions (Windows only).
<li><a href="../../samples/resource">resource</a>: shows how to use wxWindows resources (.wxr files).
<li><a href="../../samples/resource">resource</a>: shows how to use wxWidgets resources (.wxr files).
<!-- <li><a href="../../samples/richedit">richedit</a>: a work-in-progress rich text editor with plain text and HTML export
facilities.
-->
@@ -439,7 +439,7 @@ The following are fully-fledged applications.<P>
<li><a href="../../demos/dbbrowse">dbbrowse</a>: ODBC database browser application.
<li><a href="../../demos/forty">forty</a>: a great little card game by Chris Breeze.
<li><a href="../../demos/fractal">fractal</a>: fractal mountains by Andrew Davison.
<li><a href="../../demos/life">life</a>: the game of Life by J. H. Conway, implemented in wxWindows by Guillermo Rodriguez Garcia.
<li><a href="../../demos/life">life</a>: the game of Life by J. H. Conway, implemented in wxWidgets by Guillermo Rodriguez Garcia.
<li><a href="../../demos/poem">poem</a>: a little poetry display program.
</ul>

3
docs/html/platform.htm
View File

@@ -1,4 +1,3 @@
<html>
<head>
<title>Platforms supported by wxWindows 2.4</title>
@@ -92,7 +91,7 @@ often don&#39;t work.
<tr> <td bgcolor="#fafafa"><br></td><td bgcolor="#fafafa" colspan=5> All BSD systems tests are for wxGTK using gcc. </td>
<tr>
<td bgcolor="#F0F0F0" align=center valign=center rowspan=1>FreeBSD</td>
<td>all version between 3.2 and 5.0 x86</td><td align=center><IMG SRC="images/yes.gif" ALT=Ok></td><td>VZ</td><td><br></td>
<td>all versions between 3.2 and 5.1 x86</td><td align=center><IMG SRC="images/yes.gif" ALT=Ok></td><td>VZ</td><td><br></td>
</tr>
<tr>

6
docs/index.htm
View File

@@ -1,7 +1,7 @@
<HTML>
<HEAD>
<TITLE>Welcome to wxWindows 2</TITLE>
<TITLE>Welcome to wxWidgets 2</TITLE>
</HEAD>
@@ -15,7 +15,7 @@
<tr>
<td bgcolor="#660000">
<font size=+1 face="Arial, Lucida Sans, Helvetica" color="#FFFFFF">
Welcome to wxWindows 2
Welcome to wxWidgets 2
</font>
</td>
</tr>
@@ -23,7 +23,7 @@ Welcome to wxWindows 2
<P>
Welcome to wxWindows 2, the premiere cross-platform GUI C++ framework.<P>
Welcome to wxWidgets 2, the premiere cross-platform GUI C++ framework.<P>
Please click on <a href="html/index.htm">docs/html/index.htm</a> to view the main document index.<P>

30
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.
@@ -104,7 +104,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.
\membersection{wxApp::GetAuto3D}\label{wxappgetauto3d}
@@ -194,7 +194,7 @@ dialogs to pop up before the main loop has been entered).
\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}
@@ -269,7 +269,7 @@ was used}
Provide 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.
wxWidgets cleanup.
\membersection{wxApp::OnCmdLineError}\label{wxapponcmdlineerror}
@@ -346,11 +346,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.
@@ -395,7 +395,7 @@ application's main window, optionally calling
\helpref{wxApp::SetTopWindow}{wxappsettopwindow}.
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.
@@ -451,14 +451,14 @@ Under Windows, OnQueryEndSession is called in response to the WM\_QUERYENDSESSIO
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))
@@ -505,7 +505,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}
@@ -563,10 +563,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}
@@ -584,7 +584,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
@@ -232,7 +232,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.
@@ -245,7 +245,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}
@@ -257,7 +257,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.
@@ -299,7 +299,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}

126
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
@@ -135,9 +135,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 @@ Metrowerks CodeWarrior.
\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,7 +254,7 @@ 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.
@@ -264,7 +264,7 @@ The GTK and Motif ports of wxWindow can create either a static library or a shar
library on most Unix or Unix-like systems. The static library is called libwx\_gtk.a
and libwx\_motif.a whereas the name of the shared library is dependent on the
system it is created on and the version you are using. The library name for the
GTK version of wxWindows 2.2 on Linux and Solaris will be libwx\_gtk-2.2.so.0.0.0,
GTK version of wxWidgets 2.2 on Linux and Solaris will be libwx\_gtk-2.2.so.0.0.0,
on HP-UX, it will be libwx\_gtk-2.2.sl, on AIX just libwx\_gtk.a etc.
Under Windows, use the library wx.lib (release) or wxd.lib (debug) for stand-alone Windows
@@ -279,8 +279,8 @@ others can be set to minimize the size of the library. Please see the setup.h fi
and {\tt install.txt} files for details on configuration.
Under Unix (GTK and Motif) the corresponding setup.h files are generated automatically
when configuring the wxWindows using the "configure" script. When using the RPM packages
for installing wxWindows on Linux, a correct setup.h is shipped in the package and
when configuring the wxWidgets using the "configure" script. When using the RPM packages
for installing wxWidgets on Linux, a correct setup.h is shipped in the package and
this must not be changed.
\section{Makefiles}
@@ -298,7 +298,7 @@ Sample makefiles for Unix (suffix .unx), MS C++ (suffix .DOS and .NT), Borland
C++ (.BCC and .B32) and Symantec C++ (.SC) are included for the library, demos
and utilities.
The controlling makefile for wxWindows is in the MS-Windows
The controlling makefile for wxWidgets is in the MS-Windows
directory {\tt src/msw} for the different Windows compiler and
in the build directory when using the Unix ports. The build
directory can be chosen by the user. It is the directory in
@@ -311,7 +311,7 @@ Please see the platform-specific {\tt install.txt} file for further details.
\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}
@@ -323,7 +323,7 @@ is the following statement:
rcinclude "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}
@@ -356,7 +356,7 @@ STACKSIZE 8192
The only lines which will usually have to be changed per application are
NAME and DESCRIPTION.
\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,
@@ -364,7 +364,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.
@@ -372,8 +372,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
@@ -392,7 +392,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:
@@ -408,7 +408,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
@@ -421,11 +421,11 @@ The following documents some miscellaneous C++ issues.
\subsection{Templates}
wxWindows does not use templates since it is a notoriously unportable feature.
wxWidgets does not use templates since it is a notoriously unportable feature.
\subsection{RTTI}
wxWindows does not use run-time type information since wxWindows provides
wxWidgets does not use run-time type information since wxWidgets provides
its own run-time type information system, implemented using macros.
\subsection{Type of NULL}
@@ -441,7 +441,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}
@@ -449,8 +449,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.
@@ -458,7 +458,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
@@ -500,34 +500,34 @@ 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}.
@@ -602,17 +602,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.
@@ -636,13 +636,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 .wrc (wxWindows resource files) where possible, because they can be easily changed
Use .wrc (wxWidgets resource files) where possible, because they can be easily changed
independently of source code. Bitmap resources can be set up to load different
kinds of bitmap depending on platform (see the section on resource files).
@@ -691,11 +691,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.
@@ -714,7 +714,7 @@ possible it will show invalid handles being used. You may have fun seeing
what commercial programs cause these normally hidden errors! Microsoft
recommend using the debugging version of Windows, which shows up even
more problems. However, I doubt it is worth the hassle for most
applications. wxWindows is designed to minimize the possibility of such
applications. wxWidgets is designed to minimize the possibility of such
errors, but they can still happen occasionally, slipping through unnoticed
because they are not severe enough to cause a crash.

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/button.tex
View File

@@ -133,7 +133,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}}
@@ -259,7 +259,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
@@ -275,7 +275,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}
@@ -295,7 +295,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}
@@ -309,7 +309,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}
@@ -332,7 +332,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}
@@ -347,7 +347,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
@@ -367,7 +367,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}
@@ -382,7 +382,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}
@@ -442,7 +442,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}
@@ -458,7 +458,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}
@@ -493,7 +493,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}
@@ -509,7 +509,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}
@@ -526,7 +526,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}
@@ -567,7 +567,7 @@ from specifications stored in an XML format.
\overview{Database classes overview}{odbcoverview}
wxWindows provides two alternative sets of classes for accessing Microsoft's ODBC (Open Database Connectivity)
wxWidgets provides two alternative sets of classes for accessing Microsoft's ODBC (Open Database Connectivity)
product. The new version by Remstar, known as wxODBC, is more powerful,
portable, flexible and better supported, so please use the classes below for
working with databases:

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/choice.tex
View File

@@ -205,7 +205,7 @@ Gets the selected string, or the empty string if no string is selected.
{\bf Obsolescence note:} This method is obsolete and was replaced with
\helpref{GetCount}{wxchoicegetcount}, please use the new method in the new
code. This method is only available if wxWindows was compiled with
code. This method is only available if wxWidgets was compiled with
{\tt WXWIN\_COMPATIBILITY\_2\_2} defined and will disappear completely in
future versions.

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}

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

@@ -239,7 +239,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 {\it Append}. There
is only one instance of this class: {\bf wxTheColourDatabase}.
@@ -298,7 +298,7 @@ Finds a colour name given the colour. Returns NULL if not found.
\func{void}{Initialize}{\void}
Initializes the database with a number of stock colours. Called by wxWindows
Initializes the database with a number of stock colours. Called by wxWidgets
on start-up.

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

@@ -242,7 +242,7 @@ Returns the current value in the combobox text field.
{\bf Obsolescence note:} This method is obsolete and was replaced with
\helpref{GetCount}{wxcomboboxgetcount}, please use the new method in the new
code. This method is only available if wxWindows was compiled with
code. This method is only available if wxWidgets was compiled with
{\tt WXWIN\_COMPATIBILITY\_2\_2} defined and will disappear completely in
future versions.

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, wxIniConfig under Win16 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)\\
@@ -87,7 +87,7 @@ one (especially because creating a wxFileConfig object might be a time
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 wxWindows will delete this config object for you during the program
Note that wxWidgets will delete this config object for you during the program
shutdown (from \helpref{wxApp::OnExit}{wxapponexit} to be precise) but you can
also do it yourself earlier if needed.
@@ -96,7 +96,7 @@ 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

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

@@ -1,6 +1,6 @@
\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}
@@ -22,7 +22,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

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.
@@ -228,7 +228,7 @@ hotSpotY=0)}}{Constructs a cursor from a filename}
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/date.tex
View File

@@ -4,7 +4,7 @@ A class for manipulating dates.
{\bf NOTE:} this class is retained only for compatibility,
and has been replaced by \helpref{wxDateTime}{wxdatetime}. wxDate
may be withdrawn in future versions of wxWindows.
may be withdrawn in future versions of wxWidgets.
\wxheading{Derived from}

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}
@@ -1107,7 +1107,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}
@@ -110,7 +110,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}
@@ -91,7 +91,7 @@ Writes the double {\it f} to the stream using the IEEE format.
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}
@@ -1962,7 +1962,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];
@@ -3053,7 +3053,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

@@ -105,7 +105,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.
@@ -357,7 +357,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.}
@@ -951,9 +951,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/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}

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

@@ -51,10 +51,10 @@ below:
}
\end{verbatim}
A dialog may be loaded from a wxWindows resource file (extension {\tt wxr}),
A dialog may be loaded from a wxWidgets resource file (extension {\tt wxr}),
which may itself be created by Dialog Editor. For details, see
\helpref{The wxWindows resource system}{resourceformats},
\helpref{wxWindows resource functions}{resourcefuncs}
\helpref{The wxWidgets resource system}{resourceformats},
\helpref{wxWidgets resource functions}{resourcefuncs}
and the resource sample.
An application can define an \helpref{wxCloseEvent}{wxcloseevent} handler for
@@ -78,7 +78,7 @@ with {\tt NULL} parent window will be given the
style to prevent this from happening and create a really orphan dialog (note
that 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}
@@ -120,10 +120,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}

2
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}

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}.
@@ -74,7 +74,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.)
\membersection{wxEncodingConverter::Convert}\label{wxencodingconverterconvert}
@@ -106,7 +106,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.
\membersection{wxEncodingConverter::GetPlatformEquivalents}\label{wxencodingconvertergetplatformequivalents}

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

@@ -62,14 +62,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:
\begin{verbatim}

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

@@ -215,14 +215,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}
@@ -207,7 +207,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,6 +295,6 @@ 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.

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

6
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.
@@ -540,7 +540,7 @@ Make the file name absolute. This is a shortcut for
\wxheading{Note}
This method was added in wxWindows 2.4.1.
This method was added in wxWidgets 2.4.1.
\membersection{wxFileName::MakeRelativeTo}\label{wxfilenamemakerelativeto}

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

@@ -173,7 +173,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}
@@ -300,7 +300,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

@@ -106,7 +106,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.
@@ -155,7 +155,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
@@ -101,10 +101,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}.}
@@ -174,7 +174,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.}
@@ -211,7 +211,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.}
@@ -368,7 +368,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.}
@@ -398,7 +398,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.}
@@ -503,7 +503,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

8
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}
@@ -30,14 +30,14 @@ Example of using wxFTP for file downloading:
ftp.SetUser("user");
ftp.SetPassword("password");
if ( !ftp.Connect("ftp.wxwindows.org") )
if ( !ftp.Connect("ftp.wxwidgets.org") )
{
wxLogError("Couldn't connect");
return;
}
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");

104
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.
@@ -233,21 +233,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}
@@ -257,10 +257,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}
@@ -282,31 +282,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()
@@ -356,7 +356,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
@@ -796,7 +796,7 @@ directory doesn't exist).
This function is implemented for Win16 (only for drives less than 2Gb), 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}
@@ -1047,7 +1047,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
@@ -1072,7 +1072,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
@@ -1151,7 +1151,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.
@@ -1884,7 +1884,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.
@@ -2186,7 +2186,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}.
@@ -2202,7 +2202,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},
\helpref{wxDDECleanUp}{wxddecleanup}.
@@ -2534,7 +2534,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
@@ -2542,7 +2542,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}
@@ -2676,7 +2676,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:
@@ -2853,14 +2853,14 @@ result of executing an equivalent of {\tt static\_cast<classname *>(ptr)}.
\overview{Resource functions}{resourceformats}
This section details functions for manipulating wxWindows (.WXR) resource
This section details functions for manipulating wxWidgets (.WXR) resource
files and loading user interface elements from resources.
\normalbox{Please note that this use of the word `resource' is different from that used when talking
about initialisation file resource reading and writing, using such functions
as wxWriteResource and wxGetResource. It is just an unfortunate clash of terminology.}
\helponly{For an overview of the wxWindows resource mechanism, see \helpref{the wxWindows resource system}{resourceformats}.}
\helponly{For an overview of the wxWidgets resource mechanism, see \helpref{the wxWidgets resource system}{resourceformats}.}
See also \helpref{wxWindow::LoadFromResource}{wxwindowloadfromresource} for
loading from resource data.
@@ -2877,14 +2877,14 @@ perhaps for implementing resource functionality for interpreted languages.
\func{void}{wxResourceClear}{\void}
Clears the wxWindows resource table.
Clears the wxWidgets resource table.
\membersection{::wxResourceCreateBitmap}\label{wxresourcecreatebitmap}
\func{wxBitmap *}{wxResourceCreateBitmap}{\param{const wxString\& }{resource}}
Creates a new bitmap from a file, static data, or Windows resource, given a valid
wxWindows bitmap resource identifier. For example, if the .WXR file contains
wxWidgets bitmap resource identifier. For example, if the .WXR file contains
the following:
\begin{verbatim}
@@ -2904,7 +2904,7 @@ then this function can be called as follows:
\func{wxIcon *}{wxResourceCreateIcon}{\param{const wxString\& }{resource}}
Creates a new icon from a file, static data, or Windows resource, given a valid
wxWindows icon resource identifier. For example, if the .WXR file contains
wxWidgets icon resource identifier. For example, if the .WXR file contains
the following:
\begin{verbatim}
@@ -2923,7 +2923,7 @@ then this function can be called as follows:
\func{wxMenuBar *}{wxResourceCreateMenuBar}{\param{const wxString\& }{resource}}
Creates a new menu bar given a valid wxWindows menubar resource
Creates a new menu bar given a valid wxWidgets menubar resource
identifier. For example, if the .WXR file contains the following:
\begin{verbatim}
@@ -2962,10 +2962,10 @@ See \helpref{wxResourceAddIdentifier}{wxresourceaddidentifier}.
\func{bool}{wxResourceParseData}{\param{const wxString\& }{resource}, \param{wxResourceTable *}{table = NULL}}
Parses a string containing one or more wxWindows resource objects. If
Parses a string containing one or more wxWidgets resource objects. If
the resource objects are global static data that are included into the
C++ program, then this function must be called for each variable
containing the resource data, to make it known to wxWindows.
containing the resource data, to make it known to wxWidgets.
{\it resource} should contain data in the following form:
@@ -2978,7 +2978,7 @@ dialog(name = 'dialog1',
control = [1000, wxStaticBox, 'Groupbox', '0', 'group6', 5, 4, 380, 262,
[11, 'wxSWISS', 'wxNORMAL', 'wxNORMAL', 0]],
control = [1001, wxTextCtrl, '', 'wxTE_MULTILINE', 'text3',
156, 126, 200, 70, 'wxWindows is a multi-platform, GUI toolkit.',
156, 126, 200, 70, 'wxWidgets is a multi-platform, GUI toolkit.',
[11, 'wxSWISS', 'wxNORMAL', 'wxNORMAL', 0],
[11, 'wxSWISS', 'wxNORMAL', 'wxNORMAL', 0]]).
\end{verbatim}
@@ -2997,18 +2997,18 @@ of these variables should be passed to wxResourceParseData.
\func{bool}{wxResourceParseFile}{\param{const wxString\& }{filename}, \param{wxResourceTable *}{table = NULL}}
Parses a file containing one or more wxWindows resource objects
Parses a file containing one or more wxWidgets resource objects
in C++-compatible syntax. Use this function to dynamically load
wxWindows resource data.
wxWidgets resource data.
\membersection{::wxResourceParseString}\label{wxresourceparsestring}
\func{bool}{wxResourceParseString}{\param{char *}{s}, \param{wxResourceTable *}{table = NULL}}
Parses a string containing one or more wxWindows resource objects. If
Parses a string containing one or more wxWidgets resource objects. If
the resource objects are global static data that are included into the
C++ program, then this function must be called for each variable
containing the resource data, to make it known to wxWindows.
containing the resource data, to make it known to wxWidgets.
{\it resource} should contain data with the following form:
@@ -3021,7 +3021,7 @@ dialog(name = 'dialog1',
control = [1000, wxStaticBox, 'Groupbox', '0', 'group6', 5, 4, 380, 262,
[11, 'wxSWISS', 'wxNORMAL', 'wxNORMAL', 0]],
control = [1001, wxTextCtrl, '', 'wxTE_MULTILINE', 'text3',
156, 126, 200, 70, 'wxWindows is a multi-platform, GUI toolkit.',
156, 126, 200, 70, 'wxWidgets is a multi-platform, GUI toolkit.',
[11, 'wxSWISS', 'wxNORMAL', 'wxNORMAL', 0],
[11, 'wxSWISS', 'wxNORMAL', 'wxNORMAL', 0]]).
\end{verbatim}
@@ -3036,7 +3036,7 @@ load an entire {\tt .wxr file} into a string.
\func{bool}{wxResourceRegisterBitmapData}{\param{const wxString\& }{name}, \param{char **}{xpm\_data}}
Makes {\tt\#}included XBM or XPM bitmap data known to the wxWindows resource system.
Makes {\tt\#}included XBM or XPM bitmap data known to the wxWidgets resource system.
This is required if other resources will use the bitmap data, since otherwise there
is no connection between names used in resources, and the global bitmap data.
@@ -3049,7 +3049,7 @@ Another name for \helpref{wxResourceRegisterBitmapData}{registerbitmapdata}.
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}
@@ -3081,14 +3081,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}
@@ -3096,14 +3096,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}
@@ -3182,7 +3182,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
@@ -3231,7 +3231,7 @@ the value of the trace mask (possible during the run-time).
For the second function (taking a string mask), the message is logged only if
the mask has been previously enabled by the call to
\helpref{AddTraceMask}{wxlogaddtracemask}. 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)
@@ -3484,7 +3484,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.}
@@ -118,7 +118,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)\\

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

@@ -46,7 +46,7 @@ See also \helpref{SetSize}{wxhtmldcrenderersetsize}.
\wxheading{Note}
This method was added in wxWindows 2.4.1.
This method was added in wxWidgets 2.4.1.
\membersection{wxHtmlDCRenderer::SetSize}\label{wxhtmldcrenderersetsize}

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/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

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

@@ -36,7 +36,7 @@ detailed description.
\wxheading{Note}
This method was added in wxWindows 2.4.1.
This method was added in wxWidgets 2.4.1.
\membersection{wxHtmlPrintout::SetFooter}\label{wxhtmlprintoutsetfooter}

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

@@ -159,7 +159,7 @@ FALSE if an error occurred, TRUE otherwise
\wxheading{Note}
This method was added in wxWindows 2.4.1.
This method was added in wxWidgets 2.4.1.
\wxheading{See also}
@@ -327,9 +327,9 @@ platforms. Default face names are empty strings.
\wxheading{Note}
{\tt NULL} is valid value of {\it sizes} since wxWindows 2.4.1. Older
{\tt NULL} is valid value of {\it sizes} since wxWidgets 2.4.1. Older
versions did not accept {\tt NULL} value. wxHTML\_FONT\_SIZE\_n constants
were added in wxWindows 2.4.1.
were added in wxWidgets 2.4.1.
\membersection{wxHtmlWindow::SetPage}\label{wxhtmlwindowsetpage}

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

@@ -119,8 +119,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.}
@@ -141,7 +141,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
@@ -211,7 +211,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.
@@ -260,7 +260,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}
@@ -297,7 +297,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.}
@@ -307,7 +307,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/idleevt.tex
View File

@@ -41,7 +41,7 @@ Constructor.
\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

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

@@ -137,7 +137,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
@@ -208,7 +208,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}
@@ -515,7 +515,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}
@@ -584,7 +584,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:
@@ -693,7 +693,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
@@ -952,7 +952,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.

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/listbox.tex
View File

@@ -309,7 +309,7 @@ and {\tt items}.}
{\bf Obsolescence note:} This method is obsolete and was replaced with
\helpref{GetCount}{wxlistboxgetcount}, please use the new method in the new
code. This method is only available if wxWindows was compiled with
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/listview.tex
View File

@@ -5,8 +5,8 @@
%% Modified by:
%% Created: 07.11.02
%% RCS-ID: $Id$
%% Copyright: (c) 2002 Vadim Zeitlin <vadim@wxwindows.org>
%% License: wxWindows license
%% Copyright: (c) 2002 Vadim Zeitlin <vadim@wxwidgets.org>
%% 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
@@ -522,7 +522,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
@@ -541,7 +541,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}
@@ -463,9 +463,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}
@@ -490,7 +490,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.
@@ -585,7 +585,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}
@@ -614,7 +614,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}

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