Mirrors_UI_SDK/wxWidgets
1
0
Fork 0
mirror of https://github.com/wxWidgets/wxWidgets.git synced 2026-09-24 07:24:31 +08:00
Code Issues Actions 9 Packages Projects Releases Wiki Activity

Name change replacements

Browse Source 
git-svn-id: https://svn.wxwidgets.org/svn/wx/wxWidgets/trunk@27090 c3d73ce0-8a6f-49c7-b76d-6d57e0e08775
This commit is contained in:
Julian Smart
2004-05-04 08:27:20 +00:00
parent e119d0498a
commit fc2171bd4c
268 changed files with 1372 additions and 1366 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/base/readme.txt
+7 -7
View File
@@ -2,7 +2,7 @@
=============
NB: this file applies to wxBase library only. If you are using a GUI version
of wxWindows, please refer to the documentation in the appropriate
of wxWidgets, please refer to the documentation in the appropriate
subdirectory (msw, gtk, motif &c).
@@ -11,7 +11,7 @@ NB: this file applies to wxBase library only. If you are using a GUI version
0. Introduction
---------------
wxBase is the library providing most of the non-GUI classes of the wxWindows
wxBase is the library providing most of the non-GUI classes of the wxWidgets
cross-platform C++ framework. wxBase has some generic classes such as yet
another C++ string class, typesafe dynamic arrays, hashes and lists and, more
excitingly, wxDateTime -- a very flexible and powerful class for manipulating
@@ -87,7 +87,7 @@ compiler you use.
3. Installing under Unix/BeOS
-----------------------------
NB: If you're building wxBase from the wxWindows distribution and not from a
NB: If you're building wxBase from the wxWidgets distribution and not from a
separate wxBase one you will need to add "--disable-gui" to configure
arguments below!
@@ -96,7 +96,7 @@ you get any errors from the native Unix make.
The recommended way to build wxBase is:
% cd ..../wxWindows
% cd ..../wxWidgets
% mkdir base-release # or any other directory of your liking
% cd base-release
% ../configure
@@ -121,17 +121,17 @@ To build the sample then cd to samples/console and make there.
wxBase classes. It doesn't do anything useful per itself but you may want to
look at its code to see examples of usage of the class you are interested in.
There is no separate documentation for wxBase, please refer to wxWindows
There is no separate documentation for wxBase, please refer to wxWidgets
documentation instead.
Support for wxBase is available from the same places as for wxWindows itself,
Support for wxBase is available from the same places as for wxWidgets itself,
namely:
* Usenet newsgroup comp.soft-sys.wxwindows
* Mailing lists: see http://lists.wxwindows.org/ for more information
* WWW page: http://www.wxwindows.org/
* WWW page: http://www.wxwidgets.org/
Hope you will find wxBase useful!
docs/changes.txt
+17 -17
View File
@@ -1,5 +1,5 @@
----------------------------
wxWindows 2.5/2.6 Change Log
wxWidgets 2.5/2.6 Change Log
----------------------------
INCOMPATIBLE CHANGES SINCE 2.4.x
@@ -57,7 +57,7 @@ wxTaskBarIcon must be explicitly destroyed now, otherwise the application
DEPRECATED METHODS SINCE 2.4.x
==============================
Deprecated methods may still be used but will disappear in future wxWindows
Deprecated methods may still be used but will disappear in future wxWidgets
versions, please update your code to not use them.
- wxDocManager::GetNoHistoryFiles() renamed to GetHistoryFilesCount()
@@ -70,7 +70,7 @@ versions, please update your code to not use them.
- wxTheFontMapper: use wxFontMapper::Get() instead
- wxStringHashTable: use wxHashMap instead
- wxHashTableLong: use wxHashMap instead
- wxArrayString::GetStringArray: use wxCArrayString or alternative wxWindows
- wxArrayString::GetStringArray: use wxCArrayString or alternative wxWidgets
methods taking wxArrayString
- wxArrayString::Remove(index, count): use RemoveAt instead
- wxTreeItemId conversion to long is deprecated and shouldn't be used
@@ -214,7 +214,7 @@ All (GUI):
wxMSW:
- wxWindows now builds under Win64
- wxWidgets now builds under Win64
- fixed DDE memory leaks
- fixed wxTE_*WRAP styles handling
- wxTextCtrl::GetValue() works with text in non default encoding
@@ -286,7 +286,7 @@ Unix:
All:
- It is now possible to build several smaller libraries instead of single
huge wxWindows library; wxBase is now dependency of GUI ports rather then
huge wxWidgets library; wxBase is now dependency of GUI ports rather then
separately compiled library
- added wxDateSpan::operator==() and !=() (Lukasz Michalski)
- added wxFileName::GetForbiddenChars() (Dimitri Schoolwerth)
@@ -450,7 +450,7 @@ wxMSW:
- improved border handling under Windows 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.
- disable wxNB_RIGHT, wxNB_LEFT, wxNB_BOTTOM notebook styles under Windows XP
- fixed release mode build with VC 7.x (Martin Ecker)
- added support for wxALWAYS_SHOW_SB style
@@ -501,7 +501,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.
@@ -718,10 +718,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
@@ -733,7 +733,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
@@ -774,11 +774,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
@@ -967,7 +967,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
@@ -1237,7 +1237,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
@@ -1335,7 +1335,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:
@@ -1663,7 +1663,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).
@@ -1705,7 +1705,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.
docs/cocoa/install.txt
+3 -3
View File
@@ -6,19 +6,19 @@ a GCC release with Objective-C++) will be much appreciated.
For the time being, the standard configure/make method works. You will
want to build static because there are a number of unimplemented functions
that a shared library will need (becuase of wxWindows code internally using
that a shared library will need (becuase of wxWidgets code internally using
them) but that a static library will not (because most of the samples
don't need it).
On my system I have the following:
Checked out CVS source is in:
/Users/dfe/devel/wxHEADcommit/wxWindows
/Users/dfe/devel/wxHEADcommit/wxWidgets
Debug build directory is:
/Users/dfe/devel/wxHEADcommit/BUILD_COCOAd
From the debug build directory:
$ ../wxWindows/configure --with-cocoa --enable-debug --disable-shared
$ ../wxWidgets/configure --with-cocoa --enable-debug --disable-shared
$ make
$ cd samples/minimal
$ make
docs/cocoa/readme.txt
+1 -1
View File
@@ -2,7 +2,7 @@ Welcome to wxCocoa
wxCocoa is still very much a work in progress. At this point quite a bit
of functionality is working, but quite a bit is left to do. wxCocoa is not
yet suitable for a direct port of most wxWindows applications. Fortunately,
yet suitable for a direct port of most wxWidgets applications. Fortunately,
wxMac is available for those looking to move to Mac today.
If you're still reading then I assume you're interested in helping with
docs/gtk/changes.txt
+41 -41
View File
@@ -1,5 +1,5 @@
*** wxWindows 2.3.3 ***
*** wxWidgets 2.3.3 ***
Look at the General changes file for more encompassing on
the changes that have taken place in 2.3.3. This file has
@@ -78,13 +78,13 @@ wxStaticBox honours wxALIGN_XXX styles
Reworked wxConfig class interface.
Reworked wxDynamicLibary class for loading classes (particularly
wxWindows classes) from dynamic libraries.
wxWidgets classes) from dynamic libraries.
Removed wxObjectStream class.
Further improvements to wxFileName class.
*** wxWindows 2.3.2 ***
*** wxWidgets 2.3.2 ***
Addition of wxFileName class to handler DOS, Unix, Mac and VMS filenames
and paths in a platform independent way.
@@ -92,7 +92,7 @@ and paths in a platform independent way.
Addition of a wxPopupWindow class to imitate temporary windows such
as those used combo boxes or in tool tips.
Addition of wxToggleButton which was missing in wxWindows 2.2.
Addition of wxToggleButton which was missing in wxWidgets 2.2.
Support for virtual lists in wxListCtrl.
@@ -122,15 +122,15 @@ cross compilations.
Improved wxSizer-based layout system for better support for dynamic
layout.
*** wxWindows 2.3.0 ***
*** wxWidgets 2.3.0 ***
scaling for map modes other than wxMM_TEXT works correctly (Derry Bryson)
*** wxWindows 2.2.6 ***
*** wxWidgets 2.2.6 ***
wxGauge now supports wxGA_VERTICAL (Shane Forsythe)
*** 29th January 2001: wxWindows 2.2.5 released ***
*** 29th January 2001: wxWidgets 2.2.5 released ***
Synchronized with wxMSW 2.2.5, include macros
for upwards 2.4.0 compatibility.
@@ -140,7 +140,7 @@ Added missing wxEntry prototype to wx/gtk/app.h.
Fixed compilation with --enable-no_rtti/no_exceptions
with older egcs.
*** 15th January 2001: wxWindows 2.2.4 released ***
*** 15th January 2001: wxWidgets 2.2.4 released ***
Corrected wxYield() to handle recursive calls
more gracefully (and with a warning in debug mode).
@@ -172,7 +172,7 @@ Various other fixes.
Synchronized release with wxMSW again.
*** 3rd November: wxWindows 2.2.3 released ***
*** 3rd November: wxWidgets 2.2.3 released ***
Fixed bugs in HTTP code.
@@ -199,7 +199,7 @@ Updated AFM font metrics for Ghostscript fonts and let
Linux and FreeBSD default to using GS fonts (and not
Adobe fonts).
*** 20th September: wxWindows 2.2.2 released ***
*** 20th September: wxWidgets 2.2.2 released ***
Fixed wxSizer bug that made items with option
flags greater than 1 report a wrong size.
@@ -217,7 +217,7 @@ Fixed wxListCtrl::HitTest() for report mode.
Other minor fixes.
*** 20th August 2000: wxWindows 2.2.1 released ***
*** 20th August 2000: wxWidgets 2.2.1 released ***
Minor build fixes.
@@ -250,7 +250,7 @@ Minor correction to doc-view architecture.
Minor wxCommandLineParser changes.
*** 10th July 2000: wxWindows 2.2.0 released ***
*** 10th July 2000: wxWidgets 2.2.0 released ***
Added code for writing BMP images.
@@ -281,7 +281,7 @@ Various fixes to the new wxGrid class.
Bug-fixes.
*** 4th June 2000: wxWindows pre-2.2 release ***
*** 4th June 2000: wxWidgets pre-2.2 release ***
Complete freeze now. Only vital bug-fixes allowed.
@@ -293,12 +293,12 @@ Reworked wxURL.
MANY bugfixes.
*** 22th March 2000: wxWindows 2.1.15 released ***
*** 22th March 2000: wxWidgets 2.1.15 released ***
Build fix. RPMs no longer require GTK's include files.
An extra library for the OpenGl class now gets built
*** 19th March 2000: wxWindows 2.1.14 released ***
*** 19th March 2000: wxWidgets 2.1.14 released ***
An extra library for the OpenGl class now gets built
and installed. There is also an extra RPM for this
@@ -359,7 +359,7 @@ style when using the default.
The L-GPL iODBC library must now be enables explicitly so as
to not mislead people into reading the license wrong.
*** 24th January '2000: wxWindows 2.1.13 released ***
*** 24th January '2000: wxWidgets 2.1.13 released ***
Corrections to TAB handling in notebooks.
@@ -404,7 +404,7 @@ Updates to the ODBC classes (George Tasker).
Build-fixes for various platforms and compilers.
*** 6th January '2000: wxWindows 2.1.12 released ***
*** 6th January '2000: wxWidgets 2.1.12 released ***
Who has a BigEndian computer (e.g. Sparc or PowerPC) that runs a 15
and/or 16 bit colour mode? I need this for testing purposes, i.e. this
@@ -515,7 +515,7 @@ More minor changes and fixes.
Began work on a new dialog and resource editor (wxDesigner).
*** 7st November '99: wxWindows 2.1.11 released ***
*** 7st November '99: wxWidgets 2.1.11 released ***
There is still an unresolved problem with bitmap to image
conversion on big-endian architectures (such as Solaris),
@@ -524,14 +524,14 @@ one as I have no BE computer.
Enlightenment has struck the majority of the developers and
they have chosen to use the Linux kernel numbering scheme
for wxWindows from now on. This means that the next stable
release will be called wxWindows 2.2.X, development snapshots
for wxWidgets from now on. This means that the next stable
release will be called wxWidgets 2.2.X, development snapshots
will be called 2.1.X.
A lot of discussion has been wasted on how to maintain a
once released stable version. It was almost universally
agreed that only a commercial entity will have the motivation
($$$) to do that - so far there is no wxWindows Inc.
($$$) to do that - so far there is no wxWidgets Inc.
Support for GTK 1.0 has been dropped. This version has
been tested with GTK 1.2.3 and GTK 1.2.6 - it might
@@ -553,7 +553,7 @@ try again, poor AIX, HP-UX and *BSD users, but don't reckon
with immediate success. Actually, when using GNU compilers,
your chances are quite good.
My rewrite of the wxWindows underlying GTK widget
My rewrite of the wxWidgets underlying GTK widget
has turned scrolling including subwindows from barely
functional to pretty and fast. I also added scrolling
of foreign windows to wxScrolledWindow.
@@ -573,7 +573,7 @@ can now use wxODBC from wxMSW and wxGTK.
Several printing things fixed. More work needs to be done
here..
HTML widget and the wxWindows' help system based upon
HTML widget and the wxWidgets' help system based upon
it have been reorganized and improved for easier use
from Python and C++. Also HTML printing has been added.
@@ -588,14 +588,14 @@ without shadow affect).
Michael is writing a complete rewrite of the antiquated
wxGrid. This is still work-in-progress and might not make
it into wxWindows 2.2, we'll see. Help would be welcome
it into wxWidgets 2.2, we'll see. Help would be welcome
to make that happen.
Made wxMenu code lose less memory, also added wxMenu::Delete().
Added code to send wxActivateEvent to MDI windows.
Vadim added configure things to compile wxWindows without any
Vadim added configure things to compile wxWidgets without any
GUI library. This is probably work in progress. He'll also add
a wxFontEnumerator class and has enhanced wxFont to make use
of char-encodings.
@@ -823,7 +823,7 @@ Implemented global cursors and wxBusyCursor etc. Also removed
another cursor misbehaviour.
Updated many parts of the documentation to reflect changes
in wxWindows 2.1, wxPython and more exact description of
in wxWidgets 2.1, wxPython and more exact description of
cross-platform issues as well as platform differences.
Many other fixes, mainly by others...
@@ -935,7 +935,7 @@ Note that the next release might bring about changes to keyboard
handling and scroll event intercepting from wxScrolledWindow.
By and large much of the code has stabilized and won't be much
*** different in the final wxWindows 2.1 release. Please test as ***
*** different in the final wxWidgets 2.1 release. Please test as ***
much as you can.
The next release will have a new build system.
@@ -981,7 +981,7 @@ This no longer forces wxGTK applications to sleep (by having
to call usleep()) in idle time - giving more CPU slices to
the application if desired.
wxGLCanvas (the OpenGl for wxWindows) now accepts keyboard input.
wxGLCanvas (the OpenGl for wxWidgets) now accepts keyboard input.
The usual number of compile and bug fixes from all involved.
@@ -1026,7 +1026,7 @@ wxPython still doesn't compile, I think.
12th April '99: First wxGTK 2.1 snapshot released
This is the first developers' version of wxWindows 2.1 for GTK. It's main
This is the first developers' version of wxWidgets 2.1 for GTK. It's main
new feature is that it supports GTK 1.2 (as opposed to GTK 1.0) which
will make development within the GNOME environment a lot easier.
@@ -1062,16 +1062,16 @@ goodies, possibly world domination.
*** 5th March '99: wxWindows 2.0 released ***
*** 5th March '99: wxWidgets 2.0 released ***
This is the final version of wxWindows 2.0 for GTK. The versions for
This is the final version of wxWidgets 2.0 for GTK. The versions for
Windows and Motif (and also this version) are available form Julian Smart's
site. The Mac version is still under development.
*** 19th February '99: wxWindows 2.0 beta 5 ***
*** 19th February '99: wxWidgets 2.0 beta 5 ***
This is the fifth beta release and it contains mostly bug fixes and
@@ -1081,7 +1081,7 @@ Applied compile fixes for Solaris (different flavours and compilers).
*** 12th February '99: wxWindows 2.0 beta 4 ***
*** 12th February '99: wxWidgets 2.0 beta 4 ***
This is the fourth beta release and it contains mostly bug fixes and
@@ -1100,7 +1100,7 @@ Fixed many bugs. You guessed it.
*** 29th January '99: wxWindows 2.0 beta 3 ***
*** 29th January '99: wxWidgets 2.0 beta 3 ***
This is the third beta release and it contains mostly bug fixes.
@@ -1109,7 +1109,7 @@ There is one field where we haven't been able to fix the API yet, and that
it Drag'n'Drop. This is mostly due to the fact that DnD in
GTK 1.0 is hardly usable and much different from GTK 1.2 which means that
we have to design a common API for Windows, GTK 1.0 and GTK 1.2. Although
we are trying to prevent that, it is possible that wxWindows 2.0 (being
we are trying to prevent that, it is possible that wxWidgets 2.0 (being
based on GTK 1.0) will not have proper DnD support.
The major changes are that tool tips have been added, threads have been completely
@@ -1141,7 +1141,7 @@ SuSE 6.0 as SuSE decided to ship 6.0 with a broken GTK+ package.
*** 6th January '99: wxWindows 2.0 beta 2 ***
*** 6th January '99: wxWidgets 2.0 beta 2 ***
This is the second beta release and contains it mostly build and
@@ -1150,7 +1150,7 @@ commercial Unices and Windows.
*** 20th December '98: wxWindows 2.0 beta 1 ***
*** 20th December '98: wxWidgets 2.0 beta 1 ***
This is the first beta release and we have used the time before
@@ -1164,7 +1164,7 @@ program statically with wxGTK.
We changed the name of the shared library to include the version of
the GTK used so that no conflicts emerge with simultaneous
versions of wxWindows for GTK 1.0 and for GTK 1.2 and so on.
versions of wxWidgets for GTK 1.0 and for GTK 1.2 and so on.
As you can see, we have not moved to GTK 1.1.X as the different
development versions are too different and buggy to be useful. We'll
@@ -1175,7 +1175,7 @@ wxGTK now compiles without problems on anything between gcc 2.7.2 on
Linux-x86 and egcs 1.1 on Linux-Alpha and egcs 1.0 on Sparc. This isn't
as easy as it sounds...
Available form this site are the Python bindings of wxWindows.
Available form this site are the Python bindings of wxWidgets.
Thanks to Robin Dunn for this tremendous contribution.
Tkinter is dead, Java is dead, wxPython rules! That's all there is to say.
@@ -1217,9 +1217,9 @@ resulting in unexpected behaviour so it was decided to remove these
constructors.
As the number of users and the number of test programs and samples
is steadily rising the core classes of wxWindows for MSW and GTK 1.0
is steadily rising the core classes of wxWidgets for MSW and GTK 1.0
can be considered to be very stable if not outright bug-free. I haven't
seen a crash for weeks now and wxWindows' internal debug features also
seen a crash for weeks now and wxWidgets' internal debug features also
have improved every week, making stepping-through with a debugger almost
completely unnecessary as the library reports possible errors itself
(when in debug mode).
docs/gtk/install.txt
+21 -21
View File
@@ -1,4 +1,4 @@
wxWindows 2.5 for GTK installation
wxWidgets 2.5 for GTK installation
----------------------------------
IMPORTANT NOTE:
@@ -9,14 +9,14 @@ IMPORTANT NOTE:
mailing wxwin-users or the author. Preferably, try to fix the
problem first and then send a patch to the author.
When sending bug reports tell us what version of wxWindows you are
When sending bug reports tell us what version of wxWidgets you are
using (including the beta) and what compiler on what system. One
example: wxGTK 2.4.0, gcc 2.95.4, Redhat 6.2
* The simplest case
-------------------
If you compile wxWindows on Linux for the first time and don't like to read
If you compile wxWidgets on Linux for the first time and don't like to read
install instructions just do (in the base dir):
> ./configure --with-gtk
@@ -34,7 +34,7 @@ Afterwards you can continue with
> ldconfig
> exit
If you want to remove wxWindows on Unix you can do this:
If you want to remove wxWidgets on Unix you can do this:
> su <type root password>
> make uninstall
@@ -68,10 +68,10 @@ Expect problems.
* The expert case
-----------------
If you want to do some more serious cross-platform programming with wxWindows,
If you want to do some more serious cross-platform programming with wxWidgets,
such as for GTK and Motif, you can now build two complete libraries and use
them concurrently. For this end, you have to create a directory for each build
of wxWindows - you may also want to create different versions of wxWindows
of wxWidgets - you may also want to create different versions of wxWidgets
and test them concurrently. Most typically, this would be a version configured
with --enable-debug and one without. Note, that only one build can
currently be installed, so you'd have to use local version of the library for
@@ -114,7 +114,7 @@ LD_LIBRARY_PATH or equivalent variable contains the path to GTK+ libraries if
they were installed in a non default location.
You get errors from make: please use GNU make instead of the native make
program. Currently wxWindows can be built only with GNU make, BSD make and
program. Currently wxWidgets can be built only with GNU make, BSD make and
Solaris make. Other versions might work or not (any which don't have VPATH
support definitely won't).
@@ -142,7 +142,7 @@ g++ myfoo.cpp `wx-config --libs --cxxflags` -o myfoo
* General
---------
The Unix variants of wxWindows use GNU configure. If you have problems with
The Unix variants of wxWidgets use GNU configure. If you have problems with
your make use GNU make instead.
If you have general problems with installation, read my homepage at
@@ -158,7 +158,7 @@ but I tried...
* GUI libraries
---------------
wxWindows/GTK requires the GTK+ library to be installed on your system. It has
wxWidgets/GTK requires the GTK+ library to be installed on your system. It has
to be a stable version, preferably version 1.2.10 (at least 1.2.3 is required,
1.2.7 is strongly recommended).
@@ -172,7 +172,7 @@ at my homepage.
* Additional libraries
----------------------
wxWindows/Gtk requires a thread library and X libraries known to work with
wxWidgets/Gtk requires a thread library and X libraries known to work with
threads. This is the case on all commercial Unix-Variants and all
Linux-Versions that are based on glibc 2 except RedHat 5.0 which is broken in
many aspects. As of writing this, virtually all Linux distributions have
@@ -192,7 +192,7 @@ exit
Please send comments and question about the OS/2 installation
to Stefan Neis <Stefan.Neis@t-online.de> and patches to
the wxWindows mailing list.
the wxWidgets mailing list.
In the following list, the version numbers indicate the configuration that
was actually used by myself, newer version should cause no problems and
@@ -260,8 +260,8 @@ to see all the options please use:
./configure --help
It is recommended to build wxWindows in another directory (maybe a
subdirectory of your wxWindows installation) as this allows you to
It is recommended to build wxWidgets in another directory (maybe a
subdirectory of your wxWidgets installation) as this allows you to
have multiple configurations (for example, debug and release or GTK
and Motif) simultaneously.
@@ -290,9 +290,9 @@ The following options handle the kind of library you want to build.
--disable-shared Do not create shared libraries, but
build static libraries instead.
--enable-monolithic Build wxWindows as single library instead
--enable-monolithic Build wxWidgets as single library instead
of as several smaller libraries (which is
the default since wxWindows 2.5.0).
the default since wxWidgets 2.5.0).
--disable-optimise Do not optimise the code. Can
sometimes be useful for debugging
@@ -332,7 +332,7 @@ The following options handle the kind of library you want to build.
such as gdb (or its many frontends).
--enable-debug_flag Define __DEBUG__ and __WXDEBUG__ when
compiling. This enable wxWindows' very
compiling. This enable wxWidgets' very
useful internal debugging tricks (such
as automatically reporting illegal calls)
to work. Note that program and library
@@ -350,14 +350,14 @@ The following options handle the kind of library you want to build.
When producing an executable that is linked statically with wxGTK
you'll be surprised at its immense size. This can sometimes be
drastically reduced by removing features from wxWindows that
drastically reduced by removing features from wxWidgets that
are not used in your program. The most relevant such features
are
--with-odbc Enables ODBC code. This is disabled
by default because iODBC is under the
L-GPL license which is less liberal than
wxWindows license.
wxWidgets license.
--without-libpng Disables PNG image format code.
@@ -432,7 +432,7 @@ password) and type
make install
You can remove any traces of wxWindows by typing
You can remove any traces of wxWidgets by typing
make uninstall
@@ -468,14 +468,14 @@ clean:
This is certain to become the standard way unless we decide
to stick to tmake.
If your application uses only some of wxWindows libraries, you can
If your application uses only some of wxWidgets libraries, you can
specify required libraries when running wx-config. For example,
`wx-config --libs=html,core` will only output link command to link
with libraries required by core GUI classes and wxHTML classes. See
the manual for more information on the libraries.
2) The other way creates a project within the source code
directories of wxWindows. For this endeavour, you'll need
directories of wxWidgets. For this endeavour, you'll need
GNU autoconf version 2.14 and add an entry to your Makefile.in
to the bottom of the configure.in script and run autoconf
and configure before you can type make.
docs/gtk/licence.txt
+2 -2
View File
@@ -1,6 +1,6 @@
wxWindows Library License, Version 3
wxWidgets Library License, Version 3
====================================
Copyright (C) 1998 Julian Smart, Robert Roebling et al.
@@ -30,7 +30,7 @@ wxWindows Library License, Version 3
1. As a special exception, the copyright holders of this library give
permission for additional uses of the text contained in this release of
the library as licensed under the wxWindows Library License, applying
the library as licensed under the wxWidgets Library License, applying
either version 3 of the License, or (at your option) any later version of
the License as published by the copyright holders of version 3 of the
License document.
docs/gtk/readme.txt
+9 -9
View File
@@ -1,20 +1,20 @@
Welcome to wxWindows/Gtk 2.5
Welcome to wxWidgets/Gtk 2.5
You have downloaded version 2.5 of the GTK port of the
wxWindows GUI library.
wxWidgets GUI library.
wxWindows no longer supports GTK 1.0 (as did some early
wxWidgets no longer supports GTK 1.0 (as did some early
snapshots) so that you will need GTK 1.2 when using it.
GTK 1.2.6 or above is recommended although some programs
will work with GTK 1.2.3 onwards. There is now support
for GTK 2.0.
More info about the wxWindows project (including the
More info about the wxWidgets project (including the
Windows, X11/Motif and other ports) can be found at the main
wxWindows homepage at:
wxWidgets homepage at:
http://www.wxwindows.org
http://www.wxwidgets.org
Information on how to install can be found in the file
INSTALL.txt, but if you cannot wait, this should work on
@@ -56,16 +56,16 @@ libwx_gtk.a (static, only buil if --disable-shared configure
switch was used or if shared libraries are not supported at all
on your platform which is quite unlikely) and
libwx_gtk-2.2.so.0.0.0 (shared) so that once a binary
incompatible version of wxWindows/Gtk comes out we'll augment
incompatible version of wxWidgets/Gtk comes out we'll augment
the library version number to avoid linking problems.
Please send problems concerning installation, feature requests,
bug reports or comments to the wxWindows users list. Information
bug reports or comments to the wxWidgets users list. Information
on how to subscribe is available from my homepage.
Do NOT send any comments directly to me.
wxWindows/Gtk doesn't come with any guarantee whatsoever. It
wxWidgets/Gtk doesn't come with any guarantee whatsoever. It
might crash your harddisk or destroy your monitor. It doesn't
claim to be suitable for any special or general purpose.
docs/html/index.htm
+30 -30
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>
@@ -250,7 +250,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>
@@ -285,11 +285,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
@@ -297,7 +297,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 (optionally wxIniConfig), 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.
@@ -335,7 +335,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.
@@ -346,15 +346,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/notebook">notebook</a>: shows the wxNotebook (tabbed window) control.
<li><a href="../../samples/oleauto">oleauto</a>: a little OLE automation controller (Windows only; requires
Excel to be present).
@@ -394,7 +394,7 @@ wxTime, wxDate and wxVariant.
The following are deprecated samples.
<ul>
<li><a href="../../contrib/deprecated/samples/resource">resource</a>: shows how to use old-style wxWindows resources (.wxr files).
<li><a href="../../contrib/deprecated/samples/resource">resource</a>: shows how to use old-style wxWidgets resources (.wxr files).
<li><a href="../../contrib/deprecated/samples/proplist">proplist</a>: demonstrates the property list classes (a VB-style property editor).
<li><a href="../../contrib/deprecated/samples/treelay">treelay</a>: an algorithm for displaying tree hierarchies.
</ul>
@@ -421,7 +421,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>
docs/index.htm
+3 -3
View File
@@ -1,7 +1,7 @@
<HTML>
<HEAD>
<TITLE>Welcome to wxWindows 2</TITLE>
<TITLE>Welcome to wxWidgets</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
</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, 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>
docs/latex/wx/accessible.tex
+4 -4
View File
@@ -5,10 +5,10 @@
\section{\class{wxAccessible}}\label{wxaccessible}
The wxAccessible class allows wxWindows applications, and
wxWindows itself, to return extended information about user interface elements
The wxAccessible class allows wxWidgets applications, and
wxWidgets itself, to return extended information about user interface elements
to client applications such as screen readers. This is the
main way in which wxWindows implements accessibility features.
main way in which wxWidgets implements accessibility features.
At present, only Microsoft Active Accessibility is supported
by this class.
@@ -32,7 +32,7 @@ wxAccessible; for example, the sash of a splitter window.
For details on the semantics of functions and types, please refer to the
Microsoft Active Accessibility 1.2 documentation.
This class is compiled into wxWindows only if the wxUSE\_ACCESSIBILITY setup
This class is compiled into wxWidgets only if the wxUSE\_ACCESSIBILITY setup
symbol is set to 1.
\wxheading{Derived from}
docs/latex/wx/app.tex
+17 -17
View File
@@ -12,7 +12,7 @@ objects in the application.
\end{itemize}
You should use the macro IMPLEMENT\_APP(appClass) in your application implementation
file to tell wxWindows how to create an instance of your application class.
file to tell wxWidgets how to create an instance of your application class.
Use DECLARE\_APP(appClass) in a header file if you want the wxGetApp function (which returns
a reference to your application object) to be visible to other files.
@@ -112,7 +112,7 @@ Returns the application name.
\wxheading{Remarks}
wxWindows sets this to a reasonable default before
wxWidgets sets this to a reasonable default before
calling \helpref{wxApp::OnInit}{wxapponinit}, but the application can reset it at will.
@@ -200,7 +200,7 @@ the top window.
\func{int}{MainLoop}{\void}
Called by wxWindows on creation of the application. Override this if you wish
Called by wxWidgets on creation of the application. Override this if you wish
to provide your own (environment-dependent) main loop.
\wxheading{Return value}
@@ -346,7 +346,7 @@ Finally note that if the exception is rethrown from here, it can be caught in
Override this member function for any processing which needs to be
done as the application is about to exit. OnExit is called after
destroying all application windows and controls, but before
wxWindows cleanup. Note that it is not called at all if
wxWidgets cleanup. Note that it is not called at all if
\helpref{OnInit}{wxapponinit} failed.
The return value of this function is currently ignored, return the same value
@@ -381,11 +381,11 @@ work and, in fact, probably won't.
%%since this forwards OnIdle events to windows and also performs garbage collection for
%%windows whose destruction has been delayed.
%%
%%wxWindows' strategy for OnIdle processing is as follows. After pending user interface events for an
%%application have all been processed, wxWindows sends an OnIdle event to the application object. wxApp::OnIdle itself
%%wxWidgets' strategy for OnIdle processing is as follows. After pending user interface events for an
%%application have all been processed, wxWidgets sends an OnIdle event to the application object. wxApp::OnIdle itself
%%sends an OnIdle event to each application window, allowing windows to do idle processing such as updating
%%their appearance. If either wxApp::OnIdle or a window OnIdle function requested more time, by
%%calling \helpref{wxIdleEvent::RequestMore}{wxidleeventrequestmore}, wxWindows will send another OnIdle
%%calling \helpref{wxIdleEvent::RequestMore}{wxidleeventrequestmore}, wxWidgets will send another OnIdle
%%event to the application object. This will occur in a loop until either a user event is found to be
%%pending, or OnIdle requests no more time. Then all pending user events are processed until the system
%%goes idle again, when OnIdle is called, and so on.
@@ -433,7 +433,7 @@ application's main window, optionally calling
that the function returns \true.
Notice that if you want to to use the command line processing provided by
wxWindows you have to call the base class version in the derived class
wxWidgets you have to call the base class version in the derived class
OnInit().
Return \true to continue processing, \false to exit the application
@@ -488,7 +488,7 @@ Under Windows, OnQueryEndSession is called in response to the WM\_QUERYENDSESSIO
\func{virtual int}{OnRun}{\void}
This virtual function is where the execution of a program written in wxWindows
This virtual function is where the execution of a program written in wxWidgets
starts. The default implementation just enters the main loop and starts
handling the events until it terminates, either because
\helpref{ExitMainLoop}{wxappexitmainloop} has been explicitly called or because
@@ -519,14 +519,14 @@ try/catch clause around the call to the base class version there.
Windows-only function for processing a message. This function
is called from the main message loop, checking for windows that
may wish to process it. The function returns true if the message
was processed, false otherwise. If you use wxWindows with another class
was processed, false otherwise. If you use wxWidgets with another class
library with its own message loop, you should make sure that this
function is called to allow wxWindows to receive messages. For example,
function is called to allow wxWidgets to receive messages. For example,
to allow co-existence with the Microsoft Foundation Classes, override
the PreTranslateMessage function:
\begin{verbatim}
// Provide wxWindows message loop compatibility
// Provide wxWidgets message loop compatibility
BOOL CTheApp::PreTranslateMessage(MSG *msg)
{
if (wxTheApp && wxTheApp->ProcessMessage((WXMSW *)msg))
@@ -554,7 +554,7 @@ Returns true if unprocessed events are in the window system event queue.
Sends idle events to a window and its children.
Please note that this function is internal to wxWindows and shouldn't be used
Please note that this function is internal to wxWidgets and shouldn't be used
by user code.
\wxheading{Remarks}
@@ -573,7 +573,7 @@ If true is returned, more OnIdle processing is requested by one or more window.
Sets the name of the application. The name may be used in dialogs
(for example by the document/view framework). A default name is set by
wxWindows.
wxWidgets.
\wxheading{See also}
@@ -635,10 +635,10 @@ deleted. If false, the application will continue to run.}
\func{void}{SetTopWindow}{\param{wxWindow* }{window}}
Sets the `top' window. You can call this from within \helpref{wxApp::OnInit}{wxapponinit} to
let wxWindows know which is the main window. You don't have to set the top window;
let wxWidgets know which is the main window. You don't have to set the top window;
it is only a convenience so that (for example) certain dialogs without parents can use a
specific window as the top window. If no top window is specified by the application,
wxWindows just uses the first frame or dialog in its top-level window list, when it
wxWidgets just uses the first frame or dialog in its top-level window list, when it
needs to use the top window.
\wxheading{Parameters}
@@ -657,7 +657,7 @@ needs to use the top window.
Sets the name of application's vendor. The name will be used
in registry access. A default name is set by
wxWindows.
wxWidgets.
\wxheading{See also}
docs/latex/wx/array.tex
+7 -7
View File
@@ -22,7 +22,7 @@ but the price is preallocating the memory in advance. In the \helpref{memory man
you may find some useful hints about optimizing wxArray memory usage. As for executable size, all
wxArray functions are inline, so they do not take {\it any space at all}.
wxWindows has three different kinds of array. All of them derive from
wxWidgets has three different kinds of array. All of them derive from
wxBaseArray class which works with untyped data and can not be used directly.
The standard macros WX\_DEFINE\_ARRAY(), WX\_DEFINE\_SORTED\_ARRAY() and
WX\_DEFINE\_OBJARRAY() are used to define a new class deriving from it. The
@@ -39,14 +39,14 @@ deleted when the element is removed from the array. It should be noted that
all of wxArray's functions are inline, so it costs strictly nothing to define as
many array types as you want (either in terms of the executable size or the
speed) as long as at least one of them is defined and this is always the case
because wxArrays are used by wxWindows internally. This class has one serious
because wxArrays are used by wxWidgets internally. This class has one serious
limitation: it can only be used for storing integral types (bool, char, short,
int, long and their unsigned variants) or pointers (of any kind). An attempt
to use with objects of sizeof() greater than sizeof(long) will provoke a
runtime assertion failure, however declaring a wxArray of floats will not (on
the machines where sizeof(float) <= sizeof(long)), yet it will {\bf not} work,
please use wxObjArray for storing floats and doubles (NB: a more efficient
wxArrayDouble class is scheduled for the next release of wxWindows).
wxArrayDouble class is scheduled for the next release of wxWidgets).
wxSortedArray is a wxArray variant which should be used when searching in the
array is a frequently used operation. It requires you to define an additional
@@ -248,7 +248,7 @@ does exactly the same as \helpref{Item()}{wxarrayitem} method.
\func{}{WX\_DEFINE\_USER\_EXPORTED\_ARRAY}{\param{}{T}, \param{}{name}, \param{}{exportspec}}
This macro defines a new array class named {\it name} and containing the
elements of type {\it T}. The second form is used when compiling wxWindows as
elements of type {\it T}. The second form is used when compiling wxWidgets as
a DLL under Windows and array needs to be visible outside the DLL. The third is
needed for exporting an array from a user DLL.
@@ -261,7 +261,7 @@ class MyClass;
WX_DEFINE_ARRAY(MyClass *, wxArrayOfMyClass);
\end{verbatim}
Note that wxWindows predefines the following standard array classes: wxArrayInt,
Note that wxWidgets predefines the following standard array classes: wxArrayInt,
wxArrayLong and wxArrayPtrVoid.
\membersection{WX\_DEFINE\_SORTED\_ARRAY}\label{wxdefinesortedarray}
@@ -273,7 +273,7 @@ wxArrayLong and wxArrayPtrVoid.
\func{}{WX\_DEFINE\_SORTED\_USER\_EXPORTED\_ARRAY}{\param{}{T}, \param{}{name}}
This macro defines a new sorted array class named {\it name} and containing
the elements of type {\it T}. The second form is used when compiling wxWindows as
the elements of type {\it T}. The second form is used when compiling wxWidgets as
a DLL under Windows and array needs to be visible outside the DLL. The third is
needed for exporting an array from a user DLL.
@@ -315,7 +315,7 @@ wxArrayOfMyClass another(CompareMyClassObjects);
\func{}{WX\_DECLARE\_USER\_EXPORTED\_OBJARRAY}{\param{}{T}, \param{}{name}}
This macro declares a new object array class named {\it name} and containing
the elements of type {\it T}. The second form is used when compiling wxWindows as
the elements of type {\it T}. The second form is used when compiling wxWidgets as
a DLL under Windows and array needs to be visible outside the DLL. The third is
needed for exporting an array from a user DLL.
docs/latex/wx/artprov.tex
+3 -3
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}
docs/latex/wx/bbutton.tex
+2 -2
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
docs/latex/wx/bitmap.tex
+10 -10
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}
docs/latex/wx/bmpdatob.tex
+1 -1
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}
docs/latex/wx/body.tex
+70 -70
View File
@@ -3,21 +3,21 @@
\setheader{{\it CHAPTER \thechapter}}{}{}{}{}{{\it CHAPTER \thechapter}}%
\setfooter{\thepage}{}{}{}{}{\thepage}%
\section{What is wxWindows?}
\section{What is wxWidgets?}
wxWindows is a C++ framework providing GUI (Graphical User
wxWidgets is a C++ framework providing GUI (Graphical User
Interface) and other facilities on more than one platform. Version 2 currently
supports all desktop versions of MS Windows, Unix with GTK+, Unix with Motif,
and MacOS. An OS/2 port is in progress.
wxWindows was originally developed at the Artificial Intelligence
wxWidgets was originally developed at the Artificial Intelligence
Applications Institute, University of Edinburgh, for internal use,
and was first made publicly available in 1992.
Version 2 is a vastly improved version written and maintained by
Julian Smart, Robert Roebling, Vadim Zeitlin, Vaclav Slavik and many others.
This manual contains a class reference and topic overviews.
For a selection of wxWindows tutorials, please see the documentation page on the \urlref{wxWindows web site}{http://www.wxwindows.org}.
For a selection of wxWidgets tutorials, please see the documentation page on the \urlref{wxWidgets web site}{http://www.wxwidgets.org}.
Please note that in the following, ``MS Windows" often refers to all
platforms related to Microsoft Windows, including 16-bit and 32-bit
@@ -25,7 +25,7 @@ variants, unless otherwise stated. All trademarks are acknowledged.
\section{Why another cross-platform development tool?}
wxWindows was developed to provide a cheap and flexible way to maximize
wxWidgets was developed to provide a cheap and flexible way to maximize
investment in GUI application development. While a number of commercial
class libraries already existed for cross-platform development,
none met all of the following criteria:
@@ -37,14 +37,14 @@ none met all of the following criteria:
\item support for a wide range of compilers.
\end{enumerate}
Since wxWindows was started, several other free or almost-free
Since wxWidgets was started, several other free or almost-free
GUI frameworks have emerged. However, none has the range of
features, flexibility, documentation and the well-established
development team that wxWindows has.
development team that wxWidgets has.
As open source software, wxWindows has benefited from comments,
As open source software, wxWidgets has benefited from comments,
ideas, bug fixes, enhancements and the sheer enthusiasm of
users. This gives wxWindows a certain advantage over its
users. This gives wxWidgets a certain advantage over its
commercial competitors (and over free libraries without an
independent development team), plus a robustness against the
transience of one individual or company. This openness and
@@ -61,19 +61,19 @@ The importance of using a platform-independent class library
cannot be overstated, since GUI application development is very
time-consuming, and sustained popularity of particular GUIs
cannot be guaranteed. Code can very quickly become obsolete if
it addresses the wrong platform or audience. wxWindows helps to
it addresses the wrong platform or audience. wxWidgets helps to
insulate the programmer from these winds of change. Although
wxWindows may not be suitable for every application (such as an
wxWidgets may not be suitable for every application (such as an
OLE-intensive program), it provides access to most of the
functionality a GUI program normally requires, plus many extras
such as network programming, PostScript output, and HTML
rendering; and it can of course be extended as needs dictate.
As a bonus, it provides a far cleaner and easier programming
interface than the native APIs. Programmers may find it
worthwhile to use wxWindows even if they are developing on only
worthwhile to use wxWidgets even if they are developing on only
one platform.
It is impossible to sum up the functionality of wxWindows in a few paragraphs, but
It is impossible to sum up the functionality of wxWidgets in a few paragraphs, but
here are some of the benefits:
\begin{itemize}\itemsep=0pt
@@ -134,9 +134,9 @@ Additions and changes:
\end{itemize}
\end{comment}
\section{wxWindows requirements}\label{requirements}
\section{wxWidgets requirements}\label{requirements}
To make use of wxWindows, you currently need one of the following setups.
To make use of wxWidgets, you currently need one of the following setups.
(a) MS-Windows:
@@ -166,22 +166,22 @@ If using the wxX11 port, no such widget set is required.
\item At least 60 MB of disk space.
\end{enumerate}
\section{Availability and location of wxWindows}
\section{Availability and location of wxWidgets}
\winhelponly{wxWindows is available by anonymous FTP and World Wide Web
from ftp://biolpc22.york.ac.uk/pub and/or http://www.wxwindows.org.}
\winhelpignore{wxWindows is available by anonymous FTP and World Wide Web
\winhelponly{wxWidgets is available by anonymous FTP and World Wide Web
from ftp://biolpc22.york.ac.uk/pub and/or http://www.wxwidgets.org.}
\winhelpignore{wxWidgets is available by anonymous FTP and World Wide Web
from \urlref{ftp://biolpc22.york.ac.uk/pub}{ftp://biolpc22.york.ac.uk/pub}
and/or \urlref{http://www.wxwindows.org}{http://www.wxwindows.org}.}
and/or \urlref{http://www.wxwidgets.org}{http://www.wxwidgets.org}.}
You can also buy a CD-ROM using the form on the Web site.
\section{Acknowledgements}
Thanks are due to AIAI for being willing to release the original version of
wxWindows into the public domain, and to our patient partners.
wxWidgets into the public domain, and to our patient partners.
We would particularly like to thank the following for their contributions to wxWindows, and the many others who have been involved in
We would particularly like to thank the following for their contributions to wxWidgets, and the many others who have been involved in
the project over the years. Apologies for any unintentional omissions from this list.
Yiorgos Adamopoulos, Jamshid Afshar, Alejandro Aguilar-Sierra, AIAI, Patrick Albert, Karsten Ballueder, Michael Bedward, Kai Bendorf, Yura Bidus, Keith
@@ -212,18 +212,18 @@ written prior permission. M.I.T. makes no representations about the
suitability of this software for any purpose. It is provided ``as is''
without express or implied warranty.}
\chapter{Multi-platform development with wxWindows}\label{multiplat}
\chapter{Multi-platform development with wxWidgets}\label{multiplat}
\setheader{{\it CHAPTER \thechapter}}{}{}{}{}{{\it CHAPTER \thechapter}}%
\setfooter{\thepage}{}{}{}{}{\thepage}%
This chapter describes the practical details of using wxWindows. Please
This chapter describes the practical details of using wxWidgets. Please
see the file install.txt for up-to-date installation instructions, and
changes.txt for differences between versions.
\section{Include files}
The main include file is {\tt "wx/wx.h"}; this includes the most commonly
used modules of wxWindows.
used modules of wxWidgets.
To save on compilation time, include only those header files relevant to the
source file. If you are using precompiled headers, you should include
@@ -254,40 +254,40 @@ Borland precompilation is largely automatic. Visual C++ requires specification o
the file to use for precompilation. Watcom C++ is automatic apart from the specification of
the .pch file. Watcom C++ is strange in requiring the precompiled header to be used only for
object files compiled in the same directory as that in which the precompiled header was created.
Therefore, the wxWindows Watcom C++ makefiles go through hoops deleting and recreating
Therefore, the wxWidgets Watcom C++ makefiles go through hoops deleting and recreating
a single precompiled header file for each module, thus preventing an accumulation of many
multi-megabyte .pch files.
\section{Libraries}
Most ports of wxWindows can create either a static library or a shared
library. wxWindows can also be built in multilib and monolithic variants.
Most ports of wxWidgets can create either a static library or a shared
library. wxWidgets can also be built in multilib and monolithic variants.
See the \helpref{libraries list}{librarieslist} for more
information on these.
\section{Configuration}
When using project files and makefiles directly to build wxWindows,
When using project files and makefiles directly to build wxWidgets,
options are configurable in the file
\rtfsp{\tt "wx/XXX/setup.h"} where XXX is the required platform (such as msw, motif, gtk, mac). Some
settings are a matter of taste, some help with platform-specific problems, and
others can be set to minimize the size of the library. Please see the setup.h file
and {\tt install.txt} files for details on configuration.
When using the 'configure' script to configure wxWindows (on Unix and other platforms where
When using the 'configure' script to configure wxWidgets (on Unix and other platforms where
configure is available), the corresponding setup.h files are generated automatically
along with suitable makefiles. When using the RPM packages
for installing wxWindows on Linux, a correct setup.h is shipped in the package and
for installing wxWidgets on Linux, a correct setup.h is shipped in the package and
this must not be changed.
\section{Makefiles}
On Microsoft Windows, wxWindows has a different set of makefiles for each
On Microsoft Windows, wxWidgets has a different set of makefiles for each
compiler, because each compiler's 'make' tool is slightly different.
Popular Windows compilers that we cater for, and the corresponding makefile
extensions, include: Microsoft Visual C++ (.vc), Borland C++ (.bcc),
OpenWatcom C++ (.wat) and MinGW/Cygwin (.gcc). Makefiles are provided
for the wxWindows library itself, samples, demos, and utilities.
for the wxWidgets library itself, samples, demos, and utilities.
On Linux, Mac and OS/2, you use the 'configure' command to
generate the necessary makefiles. You should also use this method when
@@ -295,15 +295,15 @@ building with MinGW/Cygwin on Windows.
We also provide project files for some compilers, such as
Microsoft VC++. However, we recommend using makefiles
to build the wxWindows library itself, because makefiles
to build the wxWidgets library itself, because makefiles
can be more powerful and less manual intervention is required.
On Windows using a compiler other than MinGW/Cygwin, you would
build the wxWindows library from the build/msw directory
build the wxWidgets library from the build/msw directory
which contains the relevant makefiles.
On Windows using MinGW/Cygwin, and on Unix, MacOS X and OS/2, you invoke
'configure' (found in the top-level of the wxWindows source hierarchy),
'configure' (found in the top-level of the wxWidgets source hierarchy),
from within a suitable empty directory for containing makefiles, object files and
libraries.
@@ -313,7 +313,7 @@ xxx is the platform of interest, such as msw, gtk, x11, mac.
\section{Windows-specific files}
wxWindows application compilation under MS Windows requires at least two
wxWidgets application compilation under MS Windows requires at least two
extra files, resource and module definition files.
\subsection{Resource file}\label{resources}
@@ -325,7 +325,7 @@ is the following statement:
#include "wx/msw/wx.rc"
\end{verbatim}
which includes essential internal wxWindows definitions. The resource script
which includes essential internal wxWidgets definitions. The resource script
may also contain references to icons, cursors, etc., for example:
\begin{verbatim}
@@ -339,7 +339,7 @@ the MS Windows SDK documentation.
so programs that search your executable for icons (such
as the Program Manager) find your application icon first.}
\section{Allocating and deleting wxWindows objects}
\section{Allocating and deleting wxWidgets objects}
In general, classes derived from wxWindow must dynamically allocated
with {\it new} and deleted with {\it delete}. If you delete a window,
@@ -347,7 +347,7 @@ all of its children and descendants will be automatically deleted,
so you don't need to delete these descendants explicitly.
When deleting a frame or dialog, use {\bf Destroy} rather than {\bf delete} so
that the wxWindows delayed deletion can take effect. This waits until idle time
that the wxWidgets delayed deletion can take effect. This waits until idle time
(when all messages have been processed) to actually delete the window, to avoid
problems associated with the GUI sending events to deleted windows.
@@ -355,8 +355,8 @@ Don't create a window on the stack, because this will interfere
with delayed deletion.
If you decide to allocate a C++ array of objects (such as wxBitmap) that may
be cleaned up by wxWindows, make sure you delete the array explicitly
before wxWindows has a chance to do so on exit, since calling {\it delete} on
be cleaned up by wxWidgets, make sure you delete the array explicitly
before wxWidgets has a chance to do so on exit, since calling {\it delete} on
array members will cause memory problems.
wxColour can be created statically: it is not automatically cleaned
@@ -375,7 +375,7 @@ A problem which sometimes arises from writing multi-platform programs is that
the basic C types are not defined the same on all platforms. This holds true
for both the length in bits of the standard types (such as int and long) as
well as their byte order, which might be little endian (typically
on Intel computers) or big endian (typically on some Unix workstations). wxWindows
on Intel computers) or big endian (typically on some Unix workstations). wxWidgets
defines types and macros that make it easy to write architecture independent
code. The types are:
@@ -391,7 +391,7 @@ are described in the \helpref{Byte order macros}{byteordermacros} section.
\section{Conditional compilation}
One of the purposes of wxWindows is to reduce the need for conditional
One of the purposes of wxWidgets is to reduce the need for conditional
compilation in source code, which can be messy and confusing to follow.
However, sometimes it is necessary to incorporate platform-specific
features (such as metafile use under MS Windows). The symbols
@@ -404,12 +404,12 @@ The following documents some miscellaneous C++ issues.
\subsection{Templates}
wxWindows does not use templates (except for some advanced features that
wxWidgets does not use templates (except for some advanced features that
are switched off by default) since it is a notoriously unportable feature.
\subsection{RTTI}
wxWindows does not use C++ run-time type information since wxWindows provides
wxWidgets does not use C++ run-time type information since wxWidgets provides
its own run-time type information system, implemented using macros.
\subsection{Type of NULL}
@@ -425,7 +425,7 @@ as
\end{verbatim}
}%
It is recommended to adhere to this in all code using wxWindows as
It is recommended to adhere to this in all code using wxWidgets as
this make the code (a bit) more portable.
\subsection{Precompiled headers}
@@ -433,8 +433,8 @@ this make the code (a bit) more portable.
Some compilers, such as Borland C++ and Microsoft C++, support
precompiled headers. This can save a great deal of compiling time. The
recommended approach is to precompile {\tt "wx.h"}, using this
precompiled header for compiling both wxWindows itself and any
wxWindows applications. For Windows compilers, two dummy source files
precompiled header for compiling both wxWidgets itself and any
wxWidgets applications. For Windows compilers, two dummy source files
are provided (one for normal applications and one for creating DLLs)
to allow initial creation of the precompiled header.
@@ -442,7 +442,7 @@ However, there are several downsides to using precompiled headers. One
is that to take advantage of the facility, you often need to include
more header files than would normally be the case. This means that
changing a header file will cause more recompilations (in the case of
wxWindows, everything needs to be recompiled since everything includes {\tt "wx.h"}!)
wxWidgets, everything needs to be recompiled since everything includes {\tt "wx.h"}!)
A related problem is that for compilers that don't have precompiled
headers, including a lot of header files slows down compilation
@@ -484,33 +484,33 @@ dos2unix).
See also the File Functions section of the reference manual for
descriptions of miscellaneous file handling functions.
\chapter{Utilities and libraries supplied with wxWindows}\label{utilities}
\chapter{Utilities and libraries supplied with wxWidgets}\label{utilities}
\setheader{{\it CHAPTER \thechapter}}{}{}{}{}{{\it CHAPTER \thechapter}}%
\setfooter{\thepage}{}{}{}{}{\thepage}%
In addition to the core wxWindows library, a number of further
In addition to the core wxWidgets library, a number of further
libraries and utilities are supplied with each distribution.
Some are under the 'contrib' hierarchy which mirrors the
structure of the main wxWindows hierarchy. See also the 'utils'
structure of the main wxWidgets hierarchy. See also the 'utils'
hierarchy. The first place to look for documentation about
these tools and libraries is under the wxWindows 'docs' hierarchy,
these tools and libraries is under the wxWidgets 'docs' hierarchy,
for example {\tt docs/htmlhelp/fl.chm}.
For other user-contributed packages, please see the Contributions page
on the \urlref{wxWindows Web site}{http://www.wxwindows.org}.
on the \urlref{wxWidgets Web site}{http://www.wxwidgets.org}.
\begin{description}\itemsep=0pt
\item[{\bf Helpview}]
Helpview is a program for displaying wxWindows HTML
Help files. In many cases, you may wish to use the wxWindows HTML
Helpview is a program for displaying wxWidgets HTML
Help files. In many cases, you may wish to use the wxWidgets HTML
Help classes from within your application, but this provides a
handy stand-alone viewer. See \helpref{wxHTML Notes}{wxhtml} for more details.
You can find it in {\tt samples/html/helpview}.
\item[{\bf Tex2RTF}]
Supplied with wxWindows is a utility called Tex2RTF for converting\rtfsp
Supplied with wxWidgets is a utility called Tex2RTF for converting\rtfsp
\LaTeX\ manuals HTML, MS HTML Help, wxHTML Help, RTF, and Windows
Help RTF formats. Tex2RTF is used for the wxWindows manuals and can be used independently
Help RTF formats. Tex2RTF is used for the wxWidgets manuals and can be used independently
by authors wishing to create on-line and printed manuals from the same\rtfsp
\LaTeX\ source. Please see the separate documentation for Tex2RTF.
You can find it under {\tt utils/tex2rtf}.
@@ -524,8 +524,8 @@ Xnest-based display emulator for X11-based PDA applications. On some
systems, the Xnest window does not synchronise with the
'skin' window. This program can be found in {\tt utils/emulator}.
\item[{\bf Configuration Tool}]
The wxWindows Configuration Tool is a work in progress
intended to make it easier to configure wxWindows
The wxWidgets Configuration Tool is a work in progress
intended to make it easier to configure wxWidgets
features in detail. It exports setup.h configurations and will
eventually generate makefile config files. Invoking compilers is
also on the cards. Since configurations are
@@ -572,17 +572,17 @@ You can find this in {\tt contrib/src/plot}, {\tt contrib/include/wx/plot}, and
\setfooter{\thepage}{}{}{}{}{\thepage}%
This chapter is intended to list strategies that may be useful when
writing and debugging wxWindows programs. If you have any good tips,
writing and debugging wxWidgets programs. If you have any good tips,
please submit them for inclusion here.
\section{Strategies for reducing programming errors}
\subsection{Use ASSERT}
Although I haven't done this myself within wxWindows, it is good
Although I haven't done this myself within wxWidgets, it is good
practice to use ASSERT statements liberally, that check for conditions that
should or should not hold, and print out appropriate error messages.
These can be compiled out of a non-debugging version of wxWindows
These can be compiled out of a non-debugging version of wxWidgets
and your application. Using ASSERT is an example of `defensive programming':
it can alert you to problems later on.
@@ -606,13 +606,13 @@ Don't use absolute panel item positioning if you can avoid it. Different GUIs ha
very differently sized panel items. Consider using the constraint system, although this
can be complex to program.
Alternatively, you could use alternative .wrc (wxWindows resource files) on different
Alternatively, you could use alternative .wrc (wxWidgets resource files) on different
platforms, with slightly different dimensions in each. Or space your panel items out
to avoid problems.
\subsection{Use wxWindows resource files}
\subsection{Use wxWidgets resource files}
Use .xrc (wxWindows resource files) where possible, because they can be easily changed
Use .xrc (wxWidgets resource files) where possible, because they can be easily changed
independently of source code.
\section{Strategies for debugging}\label{debugstrategies}
@@ -660,11 +660,11 @@ Using tracing statements may be more convenient than using the debugger
in some circumstances (such as when your debugger doesn't support a lot
of debugging code, or you wish to print a bunch of variables).
\subsection{Use the wxWindows debugging facilities}
\subsection{Use the wxWidgets debugging facilities}
You can use wxDebugContext to check for
memory leaks and corrupt memory: in fact in debugging mode, wxWindows will
automatically check for memory leaks at the end of the program if wxWindows is suitably
memory leaks and corrupt memory: in fact in debugging mode, wxWidgets will
automatically check for memory leaks at the end of the program if wxWidgets is suitably
configured. Depending on the operating system and compiler, more or less
specific information about the problem will be logged.
docs/latex/wx/brush.tex
+7 -7
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.
docs/latex/wx/bufferdc.tex
+1 -1
View File
@@ -6,7 +6,7 @@
%% Created: 07.02.04
%% RCS-ID: $Id$
%% Copyright: (c) 2004 Vadim Zeitlin
%% License: wxWindows license
%% License: wxWidgets license
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\section{\class{wxBufferedDC}}\label{wxbuffereddc}
docs/latex/wx/button.tex
+1 -1
View File
@@ -134,7 +134,7 @@ Note that under Motif, calling this function immediately after
creation of a button and before the creation of other buttons
will cause misalignment of the row of buttons, since default
buttons are larger. To get around this, call {\it SetDefault}\rtfsp
after you have created a row of buttons: wxWindows will
after you have created a row of buttons: wxWidgets will
then set the size of all buttons currently on the panel to
the same size.
docs/latex/wx/calctrl.tex
+1 -1
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}
docs/latex/wx/caret.tex
+1 -1
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}
docs/latex/wx/category.tex
+15 -15
View File
@@ -2,7 +2,7 @@
\setheader{{\it CHAPTER \thechapter}}{}{}{}{}{{\it CHAPTER \thechapter}}%
\setfooter{\thepage}{}{}{}{}{\thepage}%
A classification of wxWindows classes by category.
A classification of wxWidgets classes by category.
{\large {\bf Managed windows}}
@@ -267,7 +267,7 @@ user input.
{\large {\bf Data structures}}
These are the data structure classes supported by wxWindows.
These are the data structure classes supported by wxWidgets.
\twocolwidtha{6cm}
\begin{twocollist}\itemsep=0pt
@@ -282,7 +282,7 @@ These are the data structure classes supported by wxWindows.
\twocolitem{\helpref{wxList}{wxlist}}{A simple linked list implementation}
\twocolitem{\helpref{wxLongLong}{wxlonglong}}{A portable 64 bit integer type}
\twocolitem{\helpref{wxNode}{wxnode}}{Represents a node in the wxList implementation}
\twocolitem{\helpref{wxObject}{wxobject}}{The root class for most wxWindows classes}
\twocolitem{\helpref{wxObject}{wxobject}}{The root class for most wxWidgets classes}
\twocolitem{\helpref{wxPathList}{wxpathlist}}{A class to help search multiple paths}
\twocolitem{\helpref{wxPoint}{wxpoint}}{Representation of a point}
\twocolitem{\helpref{wxRect}{wxrect}}{A class representing a rectangle}
@@ -301,7 +301,7 @@ These are the data structure classes supported by wxWindows.
\overview{Overview}{runtimeclassoverview}
wxWindows supports run-time manipulation of class information, and dynamic
wxWidgets supports run-time manipulation of class information, and dynamic
creation of objects given class names.
\twocolwidtha{6cm}
@@ -315,7 +315,7 @@ creation of objects given class names.
\overview{Overview}{wxlogoverview}
wxWindows provides several classes and functions for message logging.
wxWidgets provides several classes and functions for message logging.
Please see the \helpref{wxLog overview}{wxlogoverview} for more details.
\twocolwidtha{6cm}
@@ -338,7 +338,7 @@ to redirect output sent to {\tt cout} to a \helpref{wxTextCtrl}{wxtextctrl}}
\overview{Overview}{debuggingoverview}
wxWindows supports some aspects of debugging an application through
wxWidgets supports some aspects of debugging an application through
classes, functions and macros.
\twocolwidtha{6cm}
@@ -353,7 +353,7 @@ classes, functions and macros.
{\large {\bf Networking classes}}
wxWindows provides its own classes for socket based networking.
wxWidgets provides its own classes for socket based networking.
\twocolwidtha{6cm}
\begin{twocollist}\itemsep=0pt
@@ -374,7 +374,7 @@ wxWindows provides its own classes for socket based networking.
\overview{Overview}{ipcoverview}
wxWindows provides simple interprocess communications facilities
wxWidgets provides simple interprocess communications facilities
based on Windows DDE, but available on most platforms using TCP.
\twocolwidtha{6cm}
@@ -389,7 +389,7 @@ based on Windows DDE, but available on most platforms using TCP.
\overview{Overview}{docviewoverview}
wxWindows supports a document/view framework which provides
wxWidgets supports a document/view framework which provides
housekeeping for a document-centric application.
\twocolwidtha{6cm}
@@ -449,7 +449,7 @@ facilities.
{\large {\bf File related classes}}
wxWindows has several small classes to work with disk files, see \helpref{file classes
wxWidgets has several small classes to work with disk files, see \helpref{file classes
overview}{wxfileoverview} for more details.
\twocolwidtha{6cm}
@@ -465,7 +465,7 @@ overview}{wxfileoverview} for more details.
{\large {\bf Stream classes}}
wxWindows has its own set of stream classes, as an alternative to often buggy standard stream
wxWidgets has its own set of stream classes, as an alternative to often buggy standard stream
libraries, and to provide enhanced functionality.
\twocolwidtha{6cm}
@@ -500,7 +500,7 @@ libraries, and to provide enhanced functionality.
\overview{Multithreading overview}{wxthreadoverview}
wxWindows provides a set of classes to make use of the native thread
wxWidgets provides a set of classes to make use of the native thread
capabilities of the various platforms.
\twocolwidtha{6cm}
@@ -517,7 +517,7 @@ capabilities of the various platforms.
{\large {\bf HTML classes}}
wxWindows provides a set of classes to display text in HTML format. These
wxWidgets provides a set of classes to display text in HTML format. These
class include a help system based on the HTML widget.
\twocolwidtha{6cm}
@@ -534,7 +534,7 @@ class include a help system based on the HTML widget.
{\large {\bf Virtual file system classes}}
wxWindows provides a set of classes that implement an extensible virtual file system,
wxWidgets provides a set of classes that implement an extensible virtual file system,
used internally by the HTML classes.
\twocolwidtha{6cm}
@@ -575,7 +575,7 @@ from specifications stored in an XML format.
\overview{Database classes overview}{odbcoverview}
wxWindows provides a set of classes for accessing Microsoft's ODBC (Open Database Connectivity)
wxWidgets provides a set of classes for accessing Microsoft's ODBC (Open Database Connectivity)
product, donated by Remstar. This is known as wxODBC.
\twocolwidtha{6cm}
docs/latex/wx/checklst.tex
+1 -1
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}.
docs/latex/wx/clasinfo.tex
+1 -1
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}
docs/latex/wx/clientdat.tex
+1 -1
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
docs/latex/wx/clipbrd.tex
+1 -1
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.
docs/latex/wx/cmdlpars.tex
+2 -2
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}
docs/latex/wx/colour.tex
+3 -3
View File
@@ -261,7 +261,7 @@ Assignment operator for the colour data.
\section{\class{wxColourDatabase}}\label{wxcolourdatabase}
wxWindows maintains a database of standard RGB colours for a predefined
wxWidgets maintains a database of standard RGB colours for a predefined
set of named colours (such as ``BLACK'', ``LIGHT GREY''). The
application may add to this set if desired by using
\helpref{AddColour}{wxcolourdatabaseaddcolour} and may use it to look up
@@ -320,7 +320,7 @@ Adds a colour to the database. If a colour with the same name already exists,
it is replaced.
Please note that the overload taking a pointer is deprecated and will be
removed in the next wxWindows version, please don't use it.
removed in the next wxWidgets version, please don't use it.
\membersection{wxColourDatabase::Find}\label{wxcolourdatabasefind}
@@ -340,7 +340,7 @@ Finds a colour given the name. Returns \tt{NULL} if not found or a pointer which
must be deleted by the caller otherwise.
Please note that this method is deprecated and will be removed in the next
wxWindows version, please use \helpref{Find}{wxcolourdatabasefind} instead of
wxWidgets version, please use \helpref{Find}{wxcolourdatabasefind} instead of
it.
docs/latex/wx/config.tex
+5 -5
View File
@@ -9,7 +9,7 @@ you're working with but you would just use the wxConfigBase methods. This
allows you to write the same code regardless of whether you're working with
the registry under Win32 or text-based config files under Unix (or even
Windows 3.1 .INI files if you're really unlucky). To make writing the portable
code even easier, wxWindows provides a typedef wxConfig
code even easier, wxWidgets provides a typedef wxConfig
which is mapped onto the native wxConfigBase implementation on the given
platform: i.e. wxRegConfig under Win32 (optionally wxIniConfig) and
wxFileConfig otherwise.
@@ -26,7 +26,7 @@ No base class
\wxheading{Include files}
<wx/config.h> (to let wxWindows choose a wxConfig class for your platform)\\
<wx/config.h> (to let wxWidgets choose a wxConfig class for your platform)\\
<wx/confbase.h> (base config class)\\
<wx/fileconf.h> (wxFileConfig class)\\
<wx/msw/regconf.h> (wxRegConfig class)\\
@@ -88,14 +88,14 @@ consuming operation). In this case, you may create this global config object
in the very start of the program and {\it Set()} it as the default. Then, from
anywhere in your program, you may access it using the {\it Get()} function.
Note that you must delete this object (usually in \helpref{wxApp::OnExit}{wxapponexit})
in order to avoid memory leaks, wxWindows won't do it automatically.
in order to avoid memory leaks, wxWidgets won't do it automatically.
As it happens, you may even further simplify the procedure described above:
you may forget about calling {\it Set()}. When {\it Get()} is called and there
is no current object, it will create one using {\it Create()} function. To
disable this behaviour {\it DontCreateOnDemand()} is provided.
{\bf Note:} You should use either {\it Set()} or {\it Get()} because wxWindows
{\bf Note:} You should use either {\it Set()} or {\it Get()} because wxWidgets
library itself would take advantage of it and could save various information
in it. For example \helpref{wxFontMapper}{wxfontmapper} or Unix version
of \helpref{wxFileDialog}{wxfiledialog} have ability to use wxConfig class.
@@ -376,7 +376,7 @@ a {\it foo} key with some backslash characters will be stored as {\tt foo=C:$\ba
of the usual storage of {\tt foo=C:$\backslash\backslash$mydir}.
The wxCONFIG\_USE\_NO\_ESCAPE\_CHARACTERS style can be helpful if your config
file must be read or written to by a non-wxWindows program (which might not
file must be read or written to by a non-wxWidgets program (which might not
understand the escape characters). Note, however, that if
wxCONFIG\_USE\_NO\_ESCAPE\_CHARACTERS style is used, it is is now
your application's responsibility to ensure that there is no newline or
docs/latex/wx/constant.tex
+1 -1
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
docs/latex/wx/cppconst.tex
+7 -7
View File
@@ -1,13 +1,13 @@
\section{Preprocesser symbols defined by wxWindows}\label{cppconst}
\section{Preprocesser symbols defined by wxWidgets}\label{cppconst}
Here is the list of preprocessor symbols used in the wxWindows source grouped
Here is the list of preprocessor symbols used in the wxWidgets source grouped
by category (and sorted by alphabetical order inside each category).
\subsection{GUI system}
\begin{twocollist}\itemsep=0pt
\twocolitem{\_\_WINDOWS\_\_}{any Windows, yom may also use \_\_WXMSW\_\_}
\twocolitem{\_\_WIN16\_\_}{Win16 API (not supported since wxWindows 2.6)}
\twocolitem{\_\_WIN16\_\_}{Win16 API (not supported since wxWidgets 2.6)}
\twocolitem{\_\_WIN32\_\_}{Win32 API}
\twocolitem{\_\_WIN95\_\_}{Windows 95 or NT 4.0 and above system (not NT 3.5x)}
\twocolitem{\_\_WXBASE\_\_}{Only wxBase, no GUI features}
@@ -26,7 +26,7 @@ defined)}
\twocolitem{\_\_WXPM\_\_}{OS/2 native Presentation Manager}
\twocolitem{\_\_WXSTUBS\_\_}{Stubbed version ('template' wxWin implementation)}
\twocolitem{\_\_WXXT\_\_}{Xt; mutually exclusive with WX\_MOTIF, not
implemented in wxWindows 2.x}
implemented in wxWidgets 2.x}
\twocolitem{\_\_WXX11\_\_}{wxX11 (\_\_WXUNIVERSAL\_\_ will be also defined)}
\twocolitem{\_\_WXWINE\_\_}{WINE (i.e. WIN32 on Unix)}
\twocolitem{\_\_WXUNIVERSAL\_\_}{wxUniversal port, always defined in addition
@@ -105,7 +105,7 @@ the compiler version, $1100$ is $11.0$ and $1200$ is OpenWatcom.}
\subsection{Miscellaneous}
\begin{twocollist}\itemsep=0pt
\twocolitem{\_\_WXWINDOWS\_\_}{always defined in wxWindows applications, see
\twocolitem{\_\_WXWINDOWS\_\_}{always defined in wxWidgets applications, see
also \helpref{wxCHECK\_VERSION}{wxcheckversion}}
\twocolitem{\_\_WXDEBUG\_\_}{defined in debug mode, undefined in release mode}
\twocolitem{wxUSE\_XXX}{if defined as $1$, feature XXX is active
@@ -114,8 +114,8 @@ also \helpref{wxCHECK\_VERSION}{wxcheckversion}}
\twocolitem{wxUSE\_GUI}{this particular feature test macro is defined to $1$
when compiling or using the library with the GUI features activated, if it is
defined as $0$, only wxBase is available.}
\twocolitem{wxUSE\_BASE}{only used by wxWindows internally (defined as $1$ when
\twocolitem{wxUSE\_BASE}{only used by wxWidgets internally (defined as $1$ when
building wxBase code, either as a standalone library or as part of the
monolithic wxWindows library, defined as $0$ when building GUI library only)}
monolithic wxWidgets library, defined as $0$ when building GUI library only)}
\end{twocollist}
docs/latex/wx/ctrlsub.tex
+3 -3
View File
@@ -6,12 +6,12 @@
%% Created: 01.01.03
%% RCS-ID: $Id$
%% Copyright: (c) 2003 Vadim Zeitlin
%% License: wxWindows license
%% License: wxWidgets license
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\section{\class{wxControlWithItems}}\label{wxcontrolwithitems}
This class is an abstract base class for some wxWindows controls which contain
This class is an abstract base class for some wxWidgets controls which contain
several items, such as \helpref{wxListBox}{wxlistbox} and
\helpref{wxCheckListBox}{wxchecklistbox} derived from it,
\helpref{wxChoice}{wxchoice} and \helpref{wxComboBox}{wxcombobox}.
@@ -264,7 +264,7 @@ Returns {\tt true} if the control is empty or {\tt false} if it has some items.
{\bf Obsolescence note:} This method is obsolete and was replaced with
\helpref{GetCount}{wxcontrolwithitemsgetcount}, please use the new method in
the new code. This method is only available if wxWindows was compiled with
the new code. This method is only available if wxWidgets was compiled with
{\tt WXWIN\_COMPATIBILITY\_2\_2} defined and will disappear completely in
future versions.
docs/latex/wx/cursor.tex
+2 -2
View File
@@ -10,7 +10,7 @@ conditional compilation will probably be required (see \helpref{wxIcon}{wxicon}
an example).
A single cursor object may be used in many windows (any subwindow type).
The wxWindows convention is to set the cursor for a window, as in X,
The wxWidgets convention is to set the cursor for a window, as in X,
rather than to set it globally as in MS Windows, although a
global \helpref{::wxSetCursor}{wxsetcursor} is also available for MS Windows use.
@@ -231,7 +231,7 @@ wxCursor down_cursor = wxCursor(down_bits, 32, 32,
Destroys the cursor. A cursor can be reused for more
than one window, and does not get destroyed when the window is
destroyed. wxWindows destroys all cursors on application exit, although
destroyed. wxWidgets destroys all cursors on application exit, although
it is best to clean them up explicitly.
\membersection{wxCursor::Ok}\label{wxcursorok}
docs/latex/wx/dataform.tex
+1 -1
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}
docs/latex/wx/dataobj.tex
+3 -3
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
docs/latex/wx/datespan.tex
+1 -1
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}
docs/latex/wx/datetime.tex
+2 -2
View File
@@ -6,7 +6,7 @@
%% Created: 07.03.00
%% RCS-ID: $Id$
%% Copyright: (c) Vadim Zeitlin
%% License: wxWindows license
%% License: wxWidgets license
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\section{\class{wxDateTime}}\label{wxdatetime}
@@ -1112,7 +1112,7 @@ the character which stopped the scan.
This function does the same as the standard ANSI C {\tt strftime(3)} function.
Please see its description for the meaning of {\it format} parameter.
It also accepts a few wxWindows-specific extensions: you can optionally specify
It also accepts a few wxWidgets-specific extensions: you can optionally specify
the width of the field to follow using {\tt printf(3)}-like syntax and the
format specification {\tt \%l} can be used to get the number of milliseconds.
docs/latex/wx/datistrm.tex
+2 -2
View File
@@ -46,7 +46,7 @@ None
\func{}{wxDataInputStream}{\param{wxInputStream\&}{ stream}, \param{wxMBConv\&}{ conv = wxMBConvUTF8}}
Constructs a datastream object from an input stream. Only read methods will
be available. The second form is only available in Unicode build of wxWindows.
be available. The second form is only available in Unicode build of wxWidgets.
\wxheading{Parameters}
@@ -135,7 +135,7 @@ Reads a string from a stream. Actually, this function first reads a long
integer specifying the length of the string (without the last null character)
and then reads the string.
In Unicode build of wxWindows, the fuction first reads multibyte (char*)
In Unicode build of wxWidgets, the fuction first reads multibyte (char*)
string from the stream and then converts it to Unicode using the {\it conv}
object passed to constructor and returns the result as wxString. You are
responsible for using the same convertor as when writing the stream.
docs/latex/wx/datostrm.tex
+2 -2
View File
@@ -26,7 +26,7 @@ None
\func{}{wxDataOutputStream}{\param{wxOutputStream\&}{ stream}, \param{wxMBConv\&}{ conv = wxMBConvUTF8}}
Constructs a datastream object from an output stream. Only write methods will
be available. The second form is only available in Unicode build of wxWindows.
be available. The second form is only available in Unicode build of wxWidgets.
\wxheading{Parameters}
@@ -116,7 +116,7 @@ specified with the {\it size} variable.
Writes {\it string} to the stream. Actually, this method writes the size of
the string before writing {\it string} itself.
In ANSI build of wxWindows, the string is written to the stream in exactly
In ANSI build of wxWidgets, the string is written to the stream in exactly
same way it is represented in memory. In Unicode build, however, the string
is first converted to multibyte representation with {\it conv} object passed
to stream's constructor (consequently, ANSI application can read data
docs/latex/wx/db.tex
+8 -8
View File
@@ -254,7 +254,7 @@ ODBC errors.}
\wxheading{Remarks}
Default cursor scrolling is defined by wxODBC\_FWD\_ONLY\_CURSORS in setup.h
when the wxWindows library is built. This behavior can be overridden when
when the wxWidgets library is built. This behavior can be overridden when
an instance of a wxDb is created (see \helpref{wxDb constructor}{wxdbconstr}).
Default setting of this value true, as not all databases/drivers support
both types of cursors.
@@ -596,7 +596,7 @@ Possible values returned by this function can be viewed in the
\helpref{Enumerated types}{wxdbenumeratedtypes} section of wxDb.
There are known issues with conformance to the ODBC standards with several
datasources supported by the wxWindows ODBC classes. Please see the overview
datasources supported by the wxWidgets ODBC classes. Please see the overview
for specific details on which datasource have which issues.
\wxheading{Return value}
@@ -731,7 +731,7 @@ of processing.
\func{bool}{IsFwdOnlyCursors}{\void}
Older form (pre-2.3/2.4 of wxWindows) of the
Older form (pre-2.3/2.4 of wxWidgets) of the
\helpref{wxDb::IsFwdOnlyCursors}{wxdbisfwdonlycursors}. This method is
provided for backward compatibility only. The method
\helpref{wxDb::IsFwdOnlyCursors}{wxdbisfwdonlycursors} should be
@@ -1093,12 +1093,12 @@ use backward scrolling cursors and their associated functions (see note above).
\wxheading{Remarks}
Added as of wxWindows v2.4 release, this function is a renamed version of
wxDb::FwdOnlyCursors() to match the normal wxWindows naming conventions for
Added as of wxWidgets v2.4 release, this function is a renamed version of
wxDb::FwdOnlyCursors() to match the normal wxWidgets naming conventions for
class member functions.
This function is not available in versions prior to v2.4. You should
use \helpref{wxDb::FwdOnlyCursors}{wxdbfwdonlycursors} for wxWindows
use \helpref{wxDb::FwdOnlyCursors}{wxdbfwdonlycursors} for wxWidgets
versions prior to 2.4.
\wxheading{See also}
@@ -1963,7 +1963,7 @@ class so a program can create a wxDbTableInf array instance to maintain all
information about all tables in the datasource to have all the datasource's
information in one memory structure.
Primarily, this class is used internally by the wxWindows ODBC classes.
Primarily, this class is used internally by the wxWidgets ODBC classes.
\begin{verbatim}
wxChar catalog[128+1];
@@ -3054,7 +3054,7 @@ calls which defined the columns accessible to this wxDbTable instance.}
\wxheading{Remarks}
NULL column support is currently not fully implemented as of wxWindows 2.4.
NULL column support is currently not fully implemented as of wxWidgets 2.4.
\membersection{wxDbTable::IsCursorClosedOnCommit}\label{wxdbtableiscursorclosedoncommit}
docs/latex/wx/dc.tex
+4 -4
View File
@@ -109,7 +109,7 @@ This sequence of operations ensures that the source's transparent area need not
and logical functions are supported.
{\bf Note:} on Windows, blitting with masks can be speeded up considerably by compiling
wxWindows with the wxUSE\_DC\_CACHE option enabled. You can also influence whether MaskBlt
wxWidgets with the wxUSE\_DC\_CACHE option enabled. You can also influence whether MaskBlt
or the explicit mask blitting code above is used, by using \helpref{wxSystemOptions}{wxsystemoptions} and
setting the {\bf no-maskblt} option to 1.
@@ -383,7 +383,7 @@ The current pen is used for drawing the outline, and the current brush
for filling the shape. Using a transparent brush suppresses filling.
The programmer is responsible for deleting the list of points.
Note that wxWindows automatically closes the first and last points.
Note that wxWidgets automatically closes the first and last points.
\pythonnote{The wxPython version of this method accepts a Python list
of wxPoint objects.}
@@ -1071,9 +1071,9 @@ The mapping mode can be one of the following:
If {\it optimize} is true (the default), this function sets optimization mode on.
This currently means that under X, the device context will not try to set a pen or brush
property if it is known to be set already. This approach can fall down
if non-wxWindows code is using the same device context or window, for example
if non-wxWidgets code is using the same device context or window, for example
when the window is a panel on which the windowing system draws panel items.
The wxWindows device context 'memory' will now be out of step with reality.
The wxWidgets device context 'memory' will now be out of step with reality.
Setting optimization off, drawing, then setting it back on again, is a trick
that must occasionally be employed.
docs/latex/wx/debugcxt.tex
+1 -1
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
docs/latex/wx/delgrend.tex
+1 -1
View File
@@ -6,7 +6,7 @@
%% Created: 11.08.03
%% RCS-ID: $Id$
%% Copyright: (c) 2003 Vadim Zeitlin <vadim@wxwindows.org>
%% License: wxWindows license
%% License: wxWidgets license
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\section{\class{wxDelegateRendererNative}}\label{wxdelegaterenderernative}
docs/latex/wx/dialevt.tex
+1 -1
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}
docs/latex/wx/dialog.tex
+3 -3
View File
@@ -77,7 +77,7 @@ with a {\tt NULL} parent window will be given the
\helpref{application's top level window}{wxappgettopwindow} as parent. Use this
style to prevent this from happening and create an orphan dialog. This is not recommended for modal dialogs.}
\twocolitem{\windowstyle{wxDIALOG\_EX\_CONTEXTHELP}}{Under Windows, puts a query button on the
caption. When pressed, Windows will go into a context-sensitive help mode and wxWindows will send
caption. When pressed, Windows will go into a context-sensitive help mode and wxWidgets will send
a wxEVT\_HELP event if the user clicked on an application window. {\it Note}\ that this is an extended
style and must be set by calling \helpref{SetExtraStyle}{wxwindowsetextrastyle} before Create is called (two-step construction).}
\end{twocollist}
@@ -119,10 +119,10 @@ Constructor.
\docparam{title}{The title of the dialog.}
\docparam{pos}{The dialog position. A value of (-1, -1) indicates a default position, chosen by
either the windowing system or wxWindows, depending on platform.}
either the windowing system or wxWidgets, depending on platform.}
\docparam{size}{The dialog size. A value of (-1, -1) indicates a default size, chosen by
either the windowing system or wxWindows, depending on platform.}
either the windowing system or wxWidgets, depending on platform.}
\docparam{style}{The window style. See \helpref{wxDialog}{wxdialog}.}
docs/latex/wx/dialup.tex
+2 -2
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.
docs/latex/wx/dir.tex
+1 -1
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}
docs/latex/wx/dirtrav.tex
+1 -1
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}

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