parse the command line, limit the number of instances of your program
executing simultaneously (portably!) and so on.
-1. Requirments and supported platforms
+1. Requirements and supported platforms
--------------------------------------
wxBase can be compiled and used under Win32, mostly any modern Unix system
some reason.
- On SGI IRIX 6.4, XtDestroyWidget in ~wxWindow causes a crash in
- some cicumstances. This is being looked into. Meanwhile, a
+ some circumstances. This is being looked into. Meanwhile, a
possible workaround is to remove the final XtDestroyWidget line in ~wxWindow
(window.cpp). This will mean that child windows will only get
destroyed when frames and dialogs are destroyed, so dynamic subwindow
if (!theTemplate)
theTemplate=templates[FilterIndex] ;
-The problem is tat FilterIndex is one based and the templates array is zero based. The correct
+The problem is that FilterIndex is one based and the templates array is zero based. The correct
thing might be to use FilterIndex-1 as the index. Else the following scenario will
cause a crash.
hard to figure out the template
when the user does not select
one of the known extensions but
-this simple fix might atleast
+this simple fix might at least
avoid the crash....
I started playing with wxMSW
just this morning and have not
yet figured out exactly how to
-submit a fix. I atleast wanted
+submit a fix. I at least wanted
to report it. Besides what I do
for the MSW might not be correct
for the other platforms :-)
FIXED+BY: Vasu Harish
IDENTIFIED+BY: Vasu Harish
PLATFORMS: wxMSW
-SHORT+DESCRIPTION: wxTextCtrl clogs output occassionally when the text size limit is reached
+SHORT+DESCRIPTION: wxTextCtrl clogs output occasionally when the text size limit is reached
WORKAROUND: In the check for (len > limit) condition in wxTextCtrl::AdjustSpaceLimit()
call, added the condition to check for the len==limit.
visitor_email_address: vasuh@bullant.net
FIXED+BY: Alexey V. Exarevsky (patched into wxWin 12/1/2000 by JACS)
IDENTIFIED+BY: Alexey V. Exarevsky
PLATFORMS: wxMSW, compiled by VC++ 6.0
-SHORT+DESCRIPTION: Print/Print preveiw to default printer in NT
+SHORT+DESCRIPTION: Print/Print preview to default printer in NT
Submit: Submit
WORKAROUND: I have moved lines that free
memory below the lines that
DATE+FIXED:
DATE+IDENTIFIED: 14/01/2000
DETAILS: I run my linux boxes headless and use a Windows box for an XServer... every sample I have tried so far
-hangs in a loop tring to get an acceptable font for something or other... here is the GDB trace
+hangs in a loop trying to get an acceptable font for something or other... here is the GDB trace
#1102 0x40203d19 in wxMessageBox ()
#1103 0x401aee31 in wxFontMapper::GetAltForEncoding ()
#1104 0x40287c45 in wxLoadQueryNearestFont ()
in the switch()es, you must rewrite them to use if()s instead
You may also define WXWIN_COMPATIBILITY_EVENT_TYPES to get the old behaviour
- but this is strongly discouraged, please consider changing your codei
+ but this is strongly discouraged, please consider changing your code
instead!
! wxDialog does not derive from wxPanel any longer - if you were using it in
your code, please update it. The quick fix for the most cases is to replace
- the occurences of wxPanel with wxWindow.
+ the occurrences of wxPanel with wxWindow.
! if you handle (and don't skip) EVT_KEY_DOWN, the EVT_CHAR event is not
generated at all, so you must call event.Skip() in your OnKeyDown() if
- fixed "missing" initial resize of wxMDIChildFrame
- wxFrame restores focus better
- Now ignore wxTHICK_FRAME in wxWindow constructor: only relevant to
- frames anddialogs, interferes with other window styles otherwise
+ frames and dialogs, interferes with other window styles otherwise
(sometimes you'd get a thick frame in a subwindow)
- wxTextCtrl insertion point set to the beginning of the control by SetValue
- Fix so wxMDIParentFrame is actually shown when Show(TRUE) is called.
- Added wxImage::Rotate.
- new wxCalendarCtrl class for picking a date interactively
-- wxMenu(Bar)::Insert() and Remove() functions for dynamic menu menagament
+- wxMenu(Bar)::Insert() and Remove() functions for dynamic menu management
- wxToolBar supports arbitrary controls (not only buttons) and can be
dynamically changed (Delete/Insert functions)
- vertical toolbars supported by MSW and GTK native wxToolBar classes
- wxScrolledWindow now has keyboard interface
- wxTextEntryDialog may be used for entering passwords (supports wxTE_PASSWORD)
- added wxEncodingConverter and improved wxFontMapper
- for dealing with convertions between different encodings,
+ for dealing with conversions between different encodings,
charsets support in wxLocale and wxHTML
- wxDragImage class added
- samples/help improved to show standard and advanced HTML help
including faster search, bookmarks, printing, setup dialog
and cross-platform binary compatible .cached files for faster
loading of large helpbooks, case insensitive search
- splitted into 3 parts: wxHtmlHelpData, Frame and Controller
+ split into 3 parts: wxHtmlHelpData, Frame and Controller
- added support for charsets and <meta> tag
- added support for font faces and justified paragraphs,
taken some steps to prepare wxHTML for frames
-- added dynamic pushing/poping of wxHtmlParser tag handlers
+- added dynamic pushing/popping of wxHtmlParser tag handlers
- improved HTML printing
- added extensive table of HTML characters substitutions ( etc.)
- fixed wxHtmlWindow flickering, several minor bugfixes
global memory operators (usually OK) and #defining new to be
WXDEBUG_NEW (sometimes it might not be OK).
- Added time.cpp to makefile; set wxUSE_DATETIME to 1.
-- Added a parent-existance check to popup menu code to make it not crash.
+- Added a parent-existence check to popup menu code to make it not crash.
- Added some optimization in wxWindow::SetSize to produce less flicker.
It remains to be seen whether this produces any resize bugs.
- wxConfig API improved, documentation updated.
- Printing classes name conventions cleaned up.
- wxUpdateUIEvent now derives from wxCommandEvent
- so event can travel up the window hierachy.
+ so event can travel up the window hierarchy.
Alpha 14, July 31st 1998
------------------------
- Added wxMouseEvent::GetPosition and
wxMouseEvent::GetLogicalPosition, both returning wxPoints.
- Made wxSize and wxRect contain longs not ints.
-- Cured some lemory leaks (thanks Vadim).
+- Cured some memory leaks (thanks Vadim).
- Tidied up OnIdle and introduced RequestMore/MoreRequested so
will only keep processing OnIdle if it returns TRUE from
MoreRequested.
implementation updated to use these base classes.
- wxHelpInstance now separated into wxHelpControllerBase (base
for all implementations), wxWinHelpController (uses standard
- WinHelp), wxXLPHelPController (talks to wxHelp by DDE or
+ WinHelp), wxXLPHelpController (talks to wxHelp by DDE or
TCP/IP). There will be others eventually, such as
wxHTMLHelpController for Microsoft (and Netscape?) HTML Help.
- Added Vadim Zeitlin's wxString class plus
Windows types where needed e.g. WXHWND.
- PrologIO revised.
- wxScrolledWindow, wxStatusBar and new MDI classes added.
- MDI is now achived using separate classes, not window styles.
+ MDI is now achieved using separate classes, not window styles.
- wxSystemSettings added, and made use of to reflect standard
Windows settings.
- SetButtonFont/SetLabelFont replaced by SetFont; font and colour
Implemented new ref-counting for GDI classes.
-New implemenation of wxCondition.
+New implementation of wxCondition.
Implemented actual comparisons between GDI classes instead of
comparing just the ref-count.
Reworked wxConfig class interface.
Reworked wxDynamicLibary class for loading classes (particularly
-wxWindows classes) from dynmic libraries.
+wxWindows classes) from dynamic libraries.
Removed wxObjectStream class.
*** wxWindows 2.3.2 ***
Addition of wxFileName class to handler DOS, Unix, Mac and VMS filenames
-and paths in a platform independant way.
+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.
Fixed some incompatibilities with GTK 1.2.10.
Partially reworked build system for installation of multiple builds and
-cross coompilations.
+cross compilations.
Improved wxSizer-based layout system for better support for dynamic
layout.
Corrected log error message box.
-Implememted wxCommandEvent::IsSelection() for wxListBox.
+Implemented wxCommandEvent::IsSelection() for wxListBox.
Corrected wxListBox::Set() for sorted mode.
Fixed bugs in HTTP code.
Implemented wxNO_FULL_REPAINT_ON_RESIZE whenever possible
-and reduced flicker a little (no longer diables GTK's own
+and reduced flicker a little (no longer disables GTK's own
anti-flicker code).
Always have a clipping region equivalent to the update
Fixed wxSizer bug that made items with option
flags greater than 1 report a wrong size.
-Fixed many incompatibilties with GTK themes -
+Fixed many incompatibilities with GTK themes -
essentially a backport from the 2.3 branch.
Added missing wxImage::Paste() for transparent
Build fix. RPMs no loner require GTK's include files.
-An extra library for the OpenGl class now gets builts
+An extra library for the OpenGl class now gets built
*** 19th March 2000: wxWindows 2.1.14 released ***
-An extra library for the OpenGl class now gets builts
+An extra library for the OpenGl class now gets built
and installed. There is also an extra RPM for this
small class now.
Renamed wx-config to wxgtk-config so that motif can be co-installed
on the same machine (with wxmotif-config).
-Speed up for drawing by resuing once created DCs instead of
+Speed up for drawing by reusing once created DCs instead of
creating and destroying them all the time.
Corrections to clipping region code (among others related to
Minor fixes for sockets related to GUI reentrance. Also
improved the IPV address class and added more error
-checking and rekated things.
+checking and related things.
Many enhancements to wxHTML, more tags supported, better support
for non-western texts etc.
Fixed keyboard handling in wxCheckListBox.
-Corrected the completely unfunctional TIFF code.
+Corrected the completely nonfunctional TIFF code.
Various minor corrections to wxWizard, wxCalendarCtrl and other
complex controls.
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
-person could help me by running a small testprogram and sending
+person could help me by running a small test program and sending
me the output.
Improved support for GTK's themes, changes in font sizes (and
where color values get exchanged. I'd need help on this
one as I have no BE computer.
-Enlightment has struck the majority of the developers and
+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
wxSpinCtrl added. Like a wxSpinButton and a wxTextCtrl.
-Changed the beaviour of the popular new wxFileDialog to
+Changed the behaviour of the popular new wxFileDialog to
not forget the once typed file name when changing the
directory.
A number of problems with compressed and socket streams have
been solved.
-Changed behavour of wxTextStream to make use of deliminators
+Changed behaviour of wxTextStream to make use of delimiters
and default to space as the standard C++ stream do.
Changes to tab traversal code to better reflect MSW code.
28th August '99: Ninth wxGTK 2.1 snapshot released
As the old makefile system didn't work, I trashed it and wrote
-a new one - mo more GNU. This, of course, caused a lot of people
+a new one - no more GNU. This, of course, caused a lot of people
to start sing their song of complaints - any change is a good
opportunity to complain, but the effect of the change is that
we now have shared library support on Linux and Solaris (and
no other tools).
Split RPMs into two, one for run-time requirements and one
-for developement (mostly headers).
+for development (mostly headers).
Addition of new layout classes that work like Java's, GTK's
or Qt`s - basically, you pack item in a box and let it tell
Implemented wxBitmapDataObject class.
-Added wxFFileStream using FILE* instead if file desrcriptor.
+Added wxFFileStream using FILE* instead if file descriptor.
Useful for creating a "cerr" like class as in normal C++.
Also added "endl" for use with wxTextStream and fixed a few
minor problems with buffered streams etc.
changed programmatically) as per wxMSW.
New implementation of wxSocket using an intermediate library called
-GSocket. This willl hopefully change in the future.
+GSocket. This will hopefully change in the future.
Reworked in-place editing of wxListCtrl and wxTreeCtrl.
New version of wxPython, of course.
-Fixed in unenclosed number of other bugs...
+Fixed an undisclosed number of other bugs...
25th June '99: Seventh wxGTK 2.1 snapshot released
-Many fixes to th new makefile system. The last version gave
+Many fixes to the new makefile system. The last version gave
immediate crashes on all Unices except Linux when linked
dynamically against an application. I reordered the object
files in the library as I guess that this was the cause.
system using automake. The main argument for switching to automake
is that the resulting makefiles should be more portable so that
people can use the native make utilities instead of GNU make. The
-new makefile sytem also handles dependencies correctly, allows for
+new makefile system also handles dependencies correctly, allows for
shared-only compilation, can be invoked from any directory for
-concurrent builds wihtin one source tree, uses libtool for greater
-shared-library platform support, has a functinonal "make uninstall",
+concurrent builds within one source tree, uses libtool for greater
+shared-library platform support, has a functional "make uninstall",
works with GTK, Motif and WINE, conforms better to GNU standards
as far as configure option names are concerned and is easier to
maintain.
times to make wxGTK work well with different micro
versions of GTK 1.2 - which is very close to impossible.
All versions give warnings, although their number might
-vary a lot. I use GTK 1.2.3 and only get wanrnings in
+vary a lot. I use GTK 1.2.3 and only get warnings in
one sample (notebook) and that one is due to a bug in
GTK - some people using GTK 1.2.2 reported hundreds of warnings
-getting spitted out for what seems like no reason.
+getting spat out for what seems like no reason.
This snapshot contains the beginnings of our merging of
headers, meaning that in the future all ports will
and a few GUI classes. Also more work has been done and window
placement and decorations etc. which we hope to have finished now.
-Applied patches for FreeBSD and SGI compilation (not yet finshed).
+Applied patches for FreeBSD and SGI compilation (not yet finished).
Updated wxPython to beta 9.
wxOLE code section using GNOME's Bonobo library (from GNOME's CVS).
New version of wxPython that works with the wxGTK 2.1.
-This now includes a very comprensive test/demo suite. Thanks to
+This now includes a very comprehensive test/demo suite. Thanks to
Robin Dunn, Harm v.d. Heijden and others. Beware of the hang-man...
More fine tuning of focus handling and GUI widgets.
Rewritten MDI subsystem.
-Correcetions and additions to the printing framework including
+Corrections and additions to the printing framework including
a paper type database (Julian).
Several controls now support more style flags for modifying
This is the first developers' version of wxWindows 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 evironment a lot easier.
+will make development within the GNOME environment a lot easier.
Apart from the move to GTK 1.2 and the changes (some major) that were
required as part of that work, enhancement or corrections have been
scrollbar, wxFrame honours Motif Window Manager hints, corrected tab
traversal for broken GTK 1.0 widgets).
-There have been slight changes to the priting dialogs and their
+There have been slight changes to the printing dialogs and their
setup data (which might break apps using this code in previous
versions). Also, a bug concerning printing white has been fixed
(actually not tested).
Although this is only the first 2.1 snapshot, there is little reason not
to use it as many bugs from version 2.0 have been corrected. There are,
-pf course, still a few problem left with GTK 1.2 (some of which relate
+of course, still a few problem left with GTK 1.2 (some of which relate
to bugs in GTK).
-I think I preserved backward compatility with GTK 1.0 and if not it
+I think I preserved backward compatibility with GTK 1.0 and if not it
should be easy to fix - but mostly I don't care.
Drag'N'Drop is currently completely broken. Also, wxPython currently
work.
Major targets for the final release (still a long way): a new configure
-system, support JPEG and GIF formats, wxHTML, super-duppah frame layout
+system, support JPEG and GIF formats, wxHTML, super-duper frame layout
stuff, syntax-highlighting editor, possibly Unicode, possibly some GNOME
-gooddies, possibly world domination.
+goodies, possibly world domination.
This is the fourth beta release and it contains mostly bug fixes and
updates for documentation.
-Tracked a few more cases, where the bahaviour between wxMSW and wxGTK
+Tracked a few more cases, where the behaviour between wxMSW and wxGTK
differed. This was the case for closing a dialog or frame as well as
for clearing a device context or setting its background colour and some
other minor details.
-Most standard dialogs have been face-liftet a little.
+Most standard dialogs have been face-lifted a little.
-Implememted default buttons for GTK.
+Implemented default buttons for GTK.
Fixed many bugs. You guessed it.
Although only a few new classes have been added, many have been polished
up substantially, the most visible are wxListCtrl, wxTreeCtrl and
all classes related to printing. Also the DialogEd now functions
-much better than before. Drag'n'Drop is fucntional but probably won't
+much better than before. Drag'n'Drop is functional but probably won't
be perfect until we use GTK 1.2 and its much improved DnD features.
wxClipboard has arrived and works for text. Other formats have not been
wxDirDialog has been added (thanks to Harm von der Heijden).
-The entite "tab traveral" system for moving from item to item in
+The entire "tab traversal" system for moving from item to item in
a dialog has been rewritten. It now completely overrides the
not-so-well-done GTK native tab system.
constructors.
As the number of users and the number of test programs and samples
-is steadialy rising the core classes of wxWindows for MSW and GTK 1.0
+is steadily rising the core classes of wxWindows 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
have improved every week, making stepping-through with a debugger almost
If you want to do some more serious cross-platform programming with wxWindows,
such as for GTK and Motif, you can now build two complete libraries and use
-them concurretly. For this end, you have to create a directory for each build
+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
and test them concurrently. Most typically, this would be a version configured
-with --enable-debug_flag and one without. Note, that only one build can currently
-be installed, so you'd have to use local version of the library for that purpose.
+with --enable-debug_flag and one without. Note, that only one build can
+currently be installed, so you'd have to use local version of the library for
+that purpose.
+
For building three versions (one GTK, one Motif and a debug version of the GTK
source) you'd do this:
You get errors during compilation: The reason is that you probably have a
broken compiler, which includes a lot of old gcc versions. In particular, if
-you use gcc 2.8 you have to disable optimsation as the compiler will give up
+you use gcc 2.8 you have to disable optimisation as the compiler will give up
with an internal compiler error.
You get immediate segfault when starting any sample or application: This is
-----------------------
wxWindows/GTK requires the GTK+ library to be installed on your system. It has
-to be a stable version, preferebly version 1.2.10 (at least 1.2.3 is required,
+to be a stable version, preferably version 1.2.10 (at least 1.2.3 is required,
1.2.7 is strongly recommended).
You can get the newest version of the GTK+ from the GTK homepage at:
If you have pthreads library installed, but have a gtk version
which does not yet support threading, you need to explicitly
-diable threading by using the option --disable-threads.
+disable threading by using the option --disable-threads.
Note that configure assumes your flex will generate files named
"lexyy.c", not "lex.yy.c". If you have a version which does
--enable-no_deps Enable compilation without creation of
dependency information.
- --enable-permissive Enable compilation without creation of
- giving erros as soon as you compile with
+ --enable-permissive Enable compilation without checking for strict
+ ANSI conformance. Useful to prevent the build
+ dying with errors as soon as you compile with
Solaris' ANSI-defying headers.
--enable-mem_tracing Add built-in memory tracing.
--disable-clipboard Disables Clipboard.
- --disable-serial Disables object instance serialiasation.
+ --disable-serial Disables object instance serialisation.
--disable-streams Disables the wxStream classes.
warning messages depending in your compiler.
If you want to be more selective, you can change into a specific
-directiry and type "make" there.
+directory and type "make" there.
-Then you may install the library and it's header files under
+Then you may install the library and its header files under
/usr/local/include/wx and /usr/local/lib respectively. You
have to log in as root (i.e. run "su" and enter the root
password) and type
rm -f *.o minimal
This is certain to become the standard way unless we decide
-to sitch to tmake.
+to stick to tmake.
2) The other way creates a project within the source code
directories of wxWindows. For this endeavour, you'll need
# and makes wxGTK.
# Call from top-level wxWindows directory.
# Note that this uses standard (but commonly-used) configure options;
-# if you're feeling braven, you may wish to compile with threads.
+# if you're feeling brave, you may wish to compile with threads.
# -- Julian Smart
rm -f *.cache
chmod a+x configure config.sub config.guess samples/configure demos/configure contrib/configure
No. This is a much-discussed topic that has (many times) ended with the conclusion that it is in
wxWindows' best interests to avoid use of templates. Not all compilers can handle
templates adequately so it would dramatically reduce the number of compilers
-and platforms that could be supported. It would also be undersirable to make
+and platforms that could be supported. It would also be undesirable to make
wxWindows dependent on another large library that may have to be downloaded and installed.
In addition, use of templates can lead to executable bloat, which is something
-wxWindows 2 is strenously trying to avoid.<P>
+wxWindows 2 is stren
uously trying to avoid.<P>
The standard C++ string class is not used, again because it is not available to all compilers,
and it is not necessarily a very efficient implementation. Also, we retain more flexibility
<li><a href="#macosx">How is the Mac OS X port different from the Classic Mac OS port?</a></li>
<li><a href="#macclassic">How are improvements to the Classic Mac OS port integrated into the Mac OS X port?</a></li>
<li><a href="#compilers">What compilers are supported?</a></li>
-<li><a href="#filetypes">How does CVS handle file types/creators under Mac OS 8.x /9.x?</a></li>
-<li><a href="#filetypesx">How does CVS handle file types/creators under Mac OS X? </a></li>
-<li><a href="#cwpro53">What steps are required to build wxMac using CodeWarrior P ro 5.3?</a></li>
+<li><a href="#filetypes">How does CVS handle file types/creators under Mac OS 8.x/9.x?</a></li>
+<li><a href="#filetypesx">How does CVS handle file types/creators under Mac OS X?</a></li>
+<li><a href="#cwpro53">What steps are required to build wxMac using CodeWarrior Pro 5.3?</a></li>
<li><a href="#buildx">What steps are required to build wxMac under Mac OS X?</a></li>
-<li><a href="#settings">What important settings are required in the CodeWarrior P roject Preferences?</a></li>
+<li><a href="#settings">What important settings are required in the CodeWarrior Project Preferences?</a></li>
<li><a href="#smarterrors">What are the smart preprocessing errors with the Apple Developer Tools?</a></li>
<li><a href="#aboutmenu">How does wxMac support the standard Apple About menu item and Help menu?</a></li>
</ul>
<h3><a name="dialoged">Does Dialog Editor work with wxWindows for Motif?</a></h3>
-Suport for Dialog Editor is almost there, but there are some wrinkles to iron
+Support for Dialog Editor is almost there, but there are some wrinkles to iron
out. You may find it's useful though: compile it and see.
<P>
and are quite simple. They do contain some Perl code, but my Perl is
primitive (very C like) so it should be possible for anybody to make
trivial modifications to it (I hope that only trivial modifications
-will be needed). I've tagged the ol makefiles as MAKEFILES_WITHOUT_TMAKE
+will be needed). I've tagged the old makefiles as MAKEFILES_WITHOUT_TMAKE
in the cvs, so you can always retrieve them and compare the new ones,
this will make it easier to solve the problems you might have.<P>
auxiliary and compendium PO files, as well as for following references into
the set of C program sources from which PO files have been derived.
It has a few special features, among which are the interactive marking
-of program strings as translatable, and the validatation of PO files
+of program strings as translatable, and the validation of PO files
with easy repositioning to PO file lines showing errors.
</P>
<P>
It is worth adding here a few words about how the maintainer should
ideally behave with PO files submissions. As a maintainer, your role is
-to authentify the origin of the submission as being the representative
+to authenticate the origin of the submission as being the representative
of the appropriate translating teams of the Translation Project (forward
the submission to <TT>`translation@iro.umontreal.ca'</TT> in case of doubt),
to ensure that the PO file format is not severely broken and does not
<P>
The ISO 639 standard defines two character codes for many countries.
-All abreviations for countries or languages used in the Translation
+All abbreviations for countries or languages used in the Translation
Project should come from this standard.
</P>
The comment lines beginning with <KBD>#,</KBD> are special because they are
not completely ignored by the programs as comments generally are. The
comma separated list of <VAR>flag</VAR>s is used by the <CODE>msgfmt</CODE>
-program to give the user some better disgnostic messages. Currently
+program to give the user some better diagnostic messages. Currently
there are two forms of flags defined:
</P>
<DT><KBD>no-c-format</KBD>
<DD>
These flags should not be added by a human. Instead only the
-<CODE>xgettext</CODE> program adds them. In an automatized PO file processing
+<CODE>xgettext</CODE> program adds them. In an automated PO file processing
system as proposed here the user changes would be thrown away again as
soon as the <CODE>xgettext</CODE> program generates a new template file.
<P>
Each of <VAR>untranslated-string</VAR> and <VAR>translated-string</VAR> respects
the C syntax for a character string, including the surrounding quotes
-and imbedded backslashed escape sequences. When the time comes
+and embedded backslashed escape sequences. When the time comes
to write multi-line strings, one should not use escaped newlines.
Instead, a closing quote should follow the last character on the
line to be continued, and an opening quote should resume the string
There are many different ways for encoding a particular string into a
PO file entry, because there are so many different ways to split and
quote multi-line strings, and even, to represent special characters
-by backslahsed escaped sequences. Some features of PO mode rely on
+by backslashed escaped sequences. Some features of PO mode rely on
the ability for PO mode to scan an already existing PO file for a
particular string encoded into the <CODE>msgid</CODE> field of some entry.
Even if PO mode has internally all the built-in machinery for
also be a problem with the notation itself which makes it impossible to
recognize whether the number is in the <CODE>"C"</CODE> locale or the local
format. This can happen if thousands separator characters are used.
-Some locales define this character accordfing to the national
+Some locales define this character according to the national
conventions to <CODE>'.'</CODE> which is the same character used in the
<CODE>"C"</CODE> locale to denote the decimal point.
<P>
While it is no problem to mark the string <CODE>"a default message"</CODE> it
is not possible to mark the string initializers for <CODE>messages</CODE>.
-What is to be done? We have to fulfill two tasks. First we have to mark the
+What is to be done? We have to fulfil two tasks. First we have to mark the
strings so that the <CODE>xgettext</CODE> program (see section <A HREF="gettext_4.html#SEC20">Invoking the <CODE>xgettext</CODE> Program</A>)
can find them, and second we have to translate the string at runtime
before printing them.
<DD>
<DT><SAMP>`--keyword[=<VAR>word</VAR>]'</SAMP>
<DD>
-Additonal keyword to be looked for (without <VAR>word</VAR> means not to
+Additional keyword to be looked for (without <VAR>word</VAR> means not to
use default keywords).
The default keywords, which are always looked for if not explicitly
<H2><A NAME="SEC21" HREF="gettext_toc.html#TOC21">C Sources Context</A></H2>
<P>
-PO mode is particularily powerful when used with PO files
+PO mode is particularly powerful when used with PO files
created through GNU <CODE>gettext</CODE> utilities, as those utilities
insert special comments in the PO files they generate.
Some of these special comments relate the PO file entry to
When the translator gets to an untranslated entry, she is fairly
often faced with an original string which is not as informative as
it normally should be, being succinct, cryptic, or otherwise ambiguous.
-Before chosing how to translate the string, she needs to understand
+Before choosing how to translate the string, she needs to understand
better what the string really means and how tight the translation has
to be. Most of times, when problems arise, the only way left to make
her judgment is looking at the true program sources from where this
It is most probable that she will still be able to find some of the
hints she needs. She will learn quickly to not feel uncomfortable
in program code, paying more attention to programmer's comments,
-variable and function names (if he dared chosing them well), and
+variable and function names (if he dared choosing them well), and
overall organization, than to programmation itself.
</P>
<P>
Each PO file entry may have a set of <STRONG>attributes</STRONG>, which are
-qualities given an name and explicitely associated with the entry
+qualities given an name and explicitly associated with the entry
translation, using a special system comment. One of these attributes
has the name <CODE>fuzzy</CODE>, and entries having this attribute are said
to have a fuzzy translation. They are called fuzzy entries, for short.
studied and compared. It is considered abnormal that one string
starts or ends with a newline while the other does not.
-Also, if the string represents a format sring used in a
+Also, if the string represents a format string used in a
<CODE>printf</CODE>-like function both strings should have the same number of
<SAMP>`%'</SAMP> format specifiers, with matching types. If the flag
<CODE>c-format</CODE> or <CODE>possible-c-format</CODE> appears in the special
very motivated at providing to themselves the pleasure of having their
beloved free software speaking their mother tongue. They do themselves
a personal favor, and do not pay that much attention to the number of
-people beneficiating of their work.
+people benefiting of their work.
<LI>Misinterpretation
was release are:
<ul>
-<li> A great number of incompatiblities between the GTK and the MSW port have been removed. This
-holds escecially true for the way, time and order, controls send notifications to the user program.
+<li> A great number of incompatibilities between the GTK and the MSW port have been removed. This
+holds especially true for the way, time and order, controls send notifications to the user program.
<li> Practically all widgets have been updated, removing bugs or adding missing features to
specific ports (mostly the GTK port).
<li> The GTK port now supports GTK version 1.2 as well as 1.0, giving access to the many new
<li> Many of the non-GUI classes have been reworked and new ones added, the stream classes
having undergone a complete rewrite.
<li> The addition of code to handle Unicode has begun and is in an advanced state.
-<li> The Python bindings (wxPython) have been largely improved and upadted to the newest
+<li> The Python bindings (wxPython) have been largely improved and updated to the newest
API and features.
</ul>
<H3><a name="publication">Publication</a></H3>
-We wll investigate publishers, especially O'Reilly. We will have to get together
+We will investigate publishers, especially O'Reilly. We will have to get together
several sample chapters to convince a publisher that the many-author approach will
work.<P>
simplicity of wxImage, you will do all kinds of image manipulation
with this class, this includes loading images in various formats
such as GIF, TIFF or JPEG (these and some more are supported by wxWindows
-without further work), analyizing the image in terms of colour usage etc
+without further work), analyzing the image in terms of colour usage etc
and applying filters to the image for higher-level manipulation, such
as blurring, sharpening etc.
doesn't pass this test as all this test does is compile and link a GTK program.
\item You get errors during compilation: The reason is that you probably have a broken
compiler, which includes almost everything that is called gcc. If you use gcc 2.8
-you have to disable optimsation as the compiler will give up with an internal
+you have to disable optimisation as the compiler will give up with an internal
compiler error.You get immediate segfault when starting any sample or application: This is either
due to having compiled the library with different flags or options than your program -
typically you might have the __WXDEBUG__ option set for the library but not for your
\wxheading{Libraries needed}
wxWindows/GTK requires the GTK+ library to be installed on your system. It has to
-be a stable version, preferebly version 1.2.3.
+be a stable version, preferably version 1.2.3.
You can get the newest version of the GTK+ from the GTK homepage at:
If you have pthreads library installed, but have a gtk version
which does not yet support threading, you need to explicitly
-diable threading by using the option --disable-threads.
+disable threading by using the option --disable-threads.
Note that configure assumes your flex will generate files named
"lexyy.c", not "lex.yy.c". If you have a version which does
--enable-no_deps Enable compilation without creation of
dependency information.
- --enable-permissive Enable compilation without creation of
- giving erros as soon as you compile with
- Solaris' ANSI-defying headers.
+ --enable-permissive Enable compilation without checking for strict
+ ANSI conformance. Useful to prevent the build
+ dying with errors as soon as you compile with
+ Solaris' ANSI-defying headers.
--enable-mem_tracing Add built-in memory tracing.
--disable-clipboard Disables Clipboard.
- --disable-serial Disables object instance serialiasation.
+ --disable-serial Disables object instance serialisation.
--disable-streams Disables the wxStream classes.
warning messages depending in your compiler.
If you want to be more selective, you can change into a specific
-directiry and type "make" there.
+directory and type "make" there.
Then you may install the library and it's header files under
/usr/local/include/wx and /usr/local/lib respectively. You
\end{verbatim}
This is certain to become the standard way unless we decide
-to sitch to tmake.
+to stick to tmake.
2) The other way creates a project within the source code
directories of wxWindows. For this endeavour, you'll need
%
% \textleftof\anybox: Sample text\endtext
% inserts "Sample text" on the left of \anybox ie \vbox, \psbox.
-% \textrightof is the symmetric (not documented, too uggly)
+% \textrightof is the symmetric (not documented, too ugly)
% Welcome any suggestion about clean wraparound macros from
% TeXhackers reading this
%
%%application have all been processed, wxWindows 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
-%%caling \helpref{wxIdleEvent::RequestMore}{wxidleeventrequestmore}, wxWindows will send another OnIdle
+%%calling \helpref{wxIdleEvent::RequestMore}{wxidleeventrequestmore}, wxWindows 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.
was processed, FALSE otherwise. If you use wxWindows 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,
-to allow co-existance with the Microsoft Foundation Classes, override
+to allow co-existence with the Microsoft Foundation Classes, override
the PreTranslateMessage function:
\begin{verbatim}
Allows the programmer to specify whether the application will use the best visual
on systems that support several visual on the same display. This is typically the
case under Solaris and IRIX, where the default visual is only 8-bit whereas certain
-appications are supposed to run in TrueColour mode.
+applications are supposed to run in TrueColour mode.
Note that this function has to be called in the constructor of the {\tt wxApp}
instance and won't have any effect when called later on.
// now that we have MyDirectory declaration in scope we may finish the
// definition of ArrayOfDirectories -- note that this expands into some C++
// code and so should only be compiled once (i.e., don't put this in the
-// header, but into a source file or you will get linkin errors)
+// header, but into a source file or you will get linking errors)
#include <wx/arrimpl.cpp> // this is a magic incantation which must be done!
WX_DEFINE_OBJARRAY(ArrayOfDirectories);
ARRAY\_MAXSIZE\_INCREMENT constant. Of course, this may lead to some memory
being wasted (ARRAY\_MAXSIZE\_INCREMENT in the worst case, i.e. 4Kb in the
current implementation), so the \helpref{Shrink()}{wxarrayshrink} function is
-provided to unallocate the extra memory. The \helpref{Alloc()}{wxarrayalloc}
+provided to deallocate the extra memory. The \helpref{Alloc()}{wxarrayalloc}
function can also be quite useful if you know in advance how many items you are
going to put in the array and will prevent the array code from reallocating the
memory more times than needed.
array.Last().MakeUpper();
\end{verbatim}
-There is also a varian of wxArrayString called wxSortedArrayString which has
+There is also a variant of wxArrayString called wxSortedArrayString which has
exactly the same methods as wxArrayString, but which always keeps the string
in it in (alphabetical) order. wxSortedArrayString uses binary search in its
-\helpref{Index}{wxarraystringindex} function (insteadf of linear search for
+\helpref{Index}{wxarraystringindex} function (instead of linear search for
wxArrayString::Index) which makes it much more efficient if you add strings to
the array rarely (because, of course, you have to pay for Index() efficiency
by having Add() be slower) but search for them often. Several methods should
-not be used with sorted array (basicly, all which break the order of items)
+not be used with sorted array (basically, all which break the order of items)
which is mentioned in their description.
Final word: none of the methods of wxArrayString is virtual including its
\constfunc{bool}{GetInstance}{\param{const wxString\&}{ classId}}
Retrieves the current object associated with a class id, and attaches the IDispatch pointer
-to this object. Returns TRUE if a pointer was succesfully retrieved, FALSE otherwise.
+to this object. Returns TRUE if a pointer was successfully retrieved, FALSE otherwise.
Note that this cannot cope with two instances of a given OLE object being active simultaneously,
such as two copies of Excel running. Which object is referenced cannot currently be specified.
You can also buy a CD-ROM using the form on the Web site.
-\section{Acknowledgments}
+\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.
create a custom attribute object and set it for the day you want to be
displayed specially (note that the control will take ownership of the pointer,
i.e. it will delete it itself). A day may be marked as being a holiday, even
-if it is not reckognized as oen by \helpref{wxDateTime}{tdateholidays} using
+if it is not recognized as one by \helpref{wxDateTime}{tdateholidays} using
\helpref{SetHoliday}{wxcalendardateattrsetholiday} method.
As the attributes are specified for each day, they may change when the month
\twocolwidtha{7cm}
\begin{twocollist}\itemsep=7pt
-\twocolitem{{\bf EVT\_CALENDAR(id, func)}}{A day was double clickedi n the calendar.}
+\twocolitem{{\bf EVT\_CALENDAR(id, func)}}{A day was double clicked in the calendar.}
\twocolitem{{\bf EVT\_CALENDAR\_SEL\_CHANGED(id, func)}}{The selected date changed.}
\twocolitem{{\bf EVT\_CALENDAR\_DAY(id, func)}}{The selected day changed.}
\twocolitem{{\bf EVT\_CALENDAR\_MONTH(id, func)}}{The selected month changed.}
\func{void}{EnableYearChange}{\param{bool }{enable = TRUE}}
This function should be used instead of changing {\tt wxCAL\_NO\_YEAR\_CHANGE}
-style bit directly. It allows or disallows the user to chaneg the year
+style bit directly. It allows or disallows the user to change the year
interactively.
\membersection{wxCalendarCtrl::EnableMonthChange}\label{wxcalendarctrlenablemonthchange}
\constfunc{const wxColour\&}{GetHolidayColourFg}{\void}
-Return the foregound colour currently used for holiday highlighting.
+Return the foreground colour currently used for holiday highlighting.
\wxheading{See also}
such events.}
\twocolitem{{\bf EVT\_TEXT\_MAXLEN(id, func)}}{Process a wxEVT\_COMMAND\_TEXT\_MAXLEN command,
which is generated by a wxTextCtrl control when the user tries to enter more
-characters into it than the limit previosuly set with
+characters into it than the limit previously set with
\helpref{SetMaxLength}{wxtextctrlsetmaxlength}.}
\twocolitem{{\bf EVT\_MENU(id, func)}}{Process a wxEVT\_COMMAND\_MENU\_SELECTED command,
which is generated by a menu item.}
Using constructors or \helpref{SetDesc}{wxcmdlineparsersetdesc} uses a (usually
{\tt const static}) table containing the command line description. If you want
-to decide which options to acccept during the run-time, using one of the
+to decide which options to accept during the run-time, using one of the
{\tt AddXXX()} functions above might be preferable.
\membersection{Customization}\label{wxcmdlineparsercustomization}
\func{void}{operator $=$}{\param{const wxColourData\&}{ data}}
-Assingment operator for the colour data.
+Assignment operator for the colour data.
\section{\class{wxColourDatabase}}\label{wxcolourdatabase}
{\it canUndo} tells the command processor whether this command is undo-able. You
can achieve the same functionality by overriding the CanUndo member function (if for example
-the criteria for undoability is context-dependant).
+the criteria for undoability is context-dependent).
{\it name} must be supplied for the command processor to display the command name
in the application's edit menu.
You must pass the same index to GetNext and GetFirst (don't modify it).
Please note that it is {\bf not} the index of the current item (you will have
-some great surprizes with wxRegConfig if you assume this) and you shouldn't
+some great surprises with wxRegConfig if you assume this) and you shouldn't
even look at it: it is just a "cookie" which stores the state of the
enumeration. It can't be stored inside the class because it would prevent you
from running several enumerations simultaneously, that's why you must pass it
\func{}{\destruct{wxCriticalSection}}{\void}
-Destructor frees the ressources.
+Destructor frees the resources.
\membersection{wxCriticalSection::Enter}\label{wxcriticalsectionenter}
Example of using it:
\begin{verbatim}
-void SetFoo()
+void Set Foo()
{
// gs_critSect is some (global) critical section guarding access to the
// object "foo"
\func{}{\destruct{wxCriticalSectionLocker}}{\void}
-Destuctor leaves the critical section.
+Destructor leaves the critical section.
\func{}{wxCursor}{\param{const wxImage\&}{ image}}
-Constructs a cursor from a wxImage. The cursor is monochome, colors with the RGB elements all greater
+Constructs a cursor from a wxImage. The cursor is monochrome, colors with the RGB elements all greater
than 127 will be foreground, colors less than this background. The mask (if any) will be used as transparent.
In MSW the foreground will be white and the background black. The cursor is resized to 32x32
\end{twocollist}}
}
-\perlnote{Contructors supported by wxPerl are:\par
+\perlnote{Constructors supported by wxPerl are:\par
\begin{itemize}
\item{Wx::Cursor->new( name, type, hotSpotX = 0, hotSpotY = 0 )}
\item{Wx::Cursor->new( id )}
which allows to distinguish between them. See
\helpref{wxDataFormat}{wxdataformat} documentation for more about formats.
-Not surprizingly, being 'smart' comes at a price of added complexity. This is
+Not surprisingly, being 'smart' comes at a price of added complexity. This is
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.
\func{static bool}{IsDSTApplicable}{\param{int }{year = Inv\_Year}, \param{Country }{country = Country\_Default}}
-Returns {\tt TRUE} if DST was usedi n the given year (the current one by
+Returns {\tt TRUE} if DST was used n the given year (the current one by
default) in the given country.
\membersection{wxDateTime::Now}\label{wxdatetimenow}
\func{static wxDateTime}{Now}{\void}
-Returns the object corresopnding to the current time.
+Returns the object corresponding to the current time.
Example:
Note that this function is accurate up to second:
\helpref{wxDateTime::UNow}{wxdatetimeunow} should be used for better precision
-(but it is less efficient and might not be availabel on all platforms).
+(but it is less efficient and might not be available on all platforms).
\wxheading{See also}
\func{static wxDateTime}{UNow}{\void}
-Returns the object corresopnding to the current time including the
+Returns the object corresponding to the current time including the
milliseconds if a function to get time with such precision is available on the
current platform (supported under most Unices and Win32).
\func{wxDateTime\&}{Set}{\param{const struct tm\& }{tm}}
-Sets the date and tiem from the broken down representation in the standard
+Sets the date and time from the broken down representation in the standard
{\tt tm} structure.
\pythonnote{Unsupported.}
By definition, the Julian Day Number, usually abbreviated as JDN, of a
particular instant is the fractional number of days since 12 hours Universal
-Coordinated Time (Greenwhich mean noon) on January 1 of the year -4712 in the
+Coordinated Time (Greenwich mean noon) on January 1 of the year -4712 in the
Julian proleptic calendar.
\pythonnote{This method is named {\tt SetJDN} in wxPython.}
\constfunc{bool}{IsBetween}{\param{const wxDateTime\& }{t1}, \param{const wxDateTime\& }{t2}}
Returns {\tt TRUE} if \helpref{IsStrictlyBetween}{wxdatetimeisstrictlybetween}
-is {\tt TRUE} or if the date is equal to one of the limi values.
+is {\tt TRUE} or if the date is equal to one of the limit values.
\wxheading{See also}
parsed. If the entire string contains only the date in RFC 822 format,
the returned pointer will be pointing to a {\tt NUL} character.
-This function is intenionally strict, it will return an error for any string
+This function is intentionally strict, it will return an error for any string
which is not RFC 822 compliant. If you need to parse date formatted in more
free ways, you should use \helpref{ParseDateTime}{wxdatetimeparsedatetime} or
\helpref{ParseDate}{wxdatetimeparsedate} instead.
It also accepts a few wxWindows-specific extensions: you can optionally specify
the width of the field to follow using {\tt printf(3)}-like syntax and the
-format specificator {\tt \%l} can be used to get the number of milliseconds.
+format specification {\tt \%l} can be used to get the number of milliseconds.
\wxheading{See also}
Sets the date to the {\it n}-th {\it weekday} in the given month of the given
year (the current month and year are used by default). The parameter {\it n}
-may be either opsitive (counting from the beginning of the month) or negative
+may be either positive (counting from the beginning of the month) or negative
(counting from the end of it).
For example, {\tt SetToWeekDay(2, wxDateTime::Wed)} will set the date to the
\section{\class{wxDataInputStream}}\label{wxdatainputstream}
This class provides functions that read binary data types in a
-portable way. Data can be read in either big-endian or litte-endian
+portable way. Data can be read in either big-endian or little-endian
format, little-endian being the default on all architectures.
If you want to read data from text files (or streams) use
\section{\class{wxDataOutputStream}}\label{wxdataoutputstream}
This class provides functions that write binary data types in a
-portable way. Data can be written in either big-endian or litte-endian
+portable way. Data can be written in either big-endian or little-endian
format, little-endian being the default on all architectures.
If you want to write data to text files (or streams) use
Older form (pre-2.3/2.4 of wxWindows) of the
\helpref{wxDb::IsFwdOnlyCursors}{wxdbisfwdonlycursors}. This method is
-provided for backward compatability only. The method
+provided for backward compatibility only. The method
\helpref{wxDb::IsFwdOnlyCursors}{wxdbisfwdonlycursors} should be
used in place of this method.
entry is recorded for the datasource connection indicating the problem
that was detected when checking for table existence. Note that it is usually
best for the calling routine to check for the existence of the table and for
-sufficent user privileges to access the table in the mode (wxDB\_QUERY\_ONLY or
+sufficient user privileges to access the table in the mode (wxDB\_QUERY\_ONLY or
!wxDB\_QUERY\_ONLY) before trying to open the table for the best possible
explanation as to why a table cannot be opened.
Gets the current user scale factor (set by \helpref{SetUserScale}{wxdcsetuserscale}).
-\perlnote{In wxPerl this method takes no arguments and returna a two element
+\perlnote{In wxPerl this method takes no arguments and return a two element
array {\tt ( x, y )}}
\membersection{wxDC::LogicalToDeviceX}\label{wxdclogicaltodevicex}
in X, text drawing isn't handled consistently with the mapping mode; a
font is always specified in point size. However, setting the {\it
user scale} (see \helpref{wxDC::SetUserScale}{wxdcsetuserscale}) scales the text appropriately. In
-Windows, scaleable TrueType fonts are always used; in X, results depend
+Windows, scalable TrueType fonts are always used; in X, results depend
on availability of fonts, but usually a reasonable match is found.
Note that the coordinate origin should ideally be selectable, but for
\section{\class{wxDCClipper}}\label{wxdcclipper}
This is a small helper class which sets the specified to its constructor
-clipping region and then automatically destroyes it in its destructor. Using
+clipping region and then automatically destroys it in its destructor. Using
it ensures that unwanted clipping region is not left set on the DC.
\wxheading{Derived from}
\func{}{\destruct{wxDCClipper}}{\void}
-Destructor: destroyes the clipping region set in the constructor.
+Destructor: destroys the clipping region set in the constructor.
\twocolitem{\windowstyle{wxSTAY\_ON\_TOP}}{The dialog stays on top of all other windows (Windows only).}
\twocolitem{\windowstyle{wxNO\_3D}}{Under Windows, specifies that the child controls
should not have 3D borders unless specified in the control.}
-\twocolitem{\windowstyle{wxDIALOG\_NO\_PARENT}}{By default, the dialogs crated
+\twocolitem{\windowstyle{wxDIALOG\_NO\_PARENT}}{By default, the dialogs created
with {\tt NULL} parent window will be given the
\helpref{applications top level window}{wxappgettopwindow} as parent. Use this
style to prevent this from happening and create a really orphan dialog (note
\end{twocollist}
Under Unix or Linux, MWM (the Motif Window Manager) or other window managers
-reckognizing the MHM hints should be running for any of these styles to have an
+recognizing the MHM hints should be running for any of these styles to have an
effect.
See also \helpref{Generic window styles}{windowstyles}.
\section{\class{wxDialUpManager}}\label{wxdialupmanager}
-This class encapsulates functions dealing with veryfying the connection status
+This class encapsulates functions dealing with verifying the connection status
of the workstation (connected to the Internet via a direct connection,
connected through a modem or not connected at all) and to establish this
connection if possible/required (i.e. in the case of the modem).
\func{bool}{Dial}{\param{const wxString\& }{nameOfISP = wxEmptyString}, \param{const wxString\& }{username = wxEmptyString}, \param{const wxString\& }{password = wxEmptyString}, \param{bool }{async = TRUE}}
-Dial the given ISP, use {\it username} and {\it password} to authentificate.
+Dial the given ISP, use {\it username} and {\it password} to authenticate.
The parameters are only used under Windows currently, for Unix you should use
\helpref{SetConnectCommand}{wxdialupmanagersetconnectcommand} to customize this
\func{bool}{EnableAutoCheckOnlineStatus}{\param{size\_t }{nSeconds = 60}}
-Enable automatical checks for the connection status and sending of
+Enable automatic checks for the connection status and sending of
{\tt wxEVT\_DIALUP\_CONNECTED/wxEVT\_DIALUP\_DISCONNECTED} events. The interval
parameter is only for Unix where we do the check manually and specifies how
often should we repeat the check (each minute by default). Under Windows, the
\func{}{\destruct{wxDir}}{\void}
-Destructor cleans up the associated ressources. It is not virtual and so this
+Destructor cleans up the associated resources. It is not virtual and so this
class is not meant to be used polymorphically.
\membersection{wxDir::Open}\label{wxdiropen}
Gets selected filename path only (else empty string).
-This function doen't count a directory as a selection.
+This function doesn't count a directory as a selection.
\membersection{wxGenericDirCtrl::GetFilter}\label{wxgenericdirctrlgetfilter}
\wxheading{Data structures}
-This header defines a platfrom-dependent {\tt wxDllType} typedef which stores
+This header defines a platform-dependent {\tt wxDllType} typedef which stores
a handle to a loaded DLLs on the given platform.
\latexignore{\rtfignore{\wxheading{Members}}}
This function loads a shared library into memory, with {\it libname} being the
name of the library: it may be either the full name including path and
-(platform-dependent) extenesion, just the basename (no path and no extension)
-or a basename with extentsion. In the last two cases, the library will be
+(platform-dependent) extension, just the basename (no path and no extension)
+or a basename with extension. In the last two cases, the library will be
searched in all standard locations.
Returns a handle to the loaded DLL. Use {\it success} parameter to test if it
\helpref{GetDataSize}{wxdataobjectsimplegetdatasize} and
\helpref{GetDataHere}{wxdataobjectsimplegetdatahere} while the objects which
may be set must override \helpref{SetData}{wxdataobjectsimplesetdata}. Of
-course, the objects supporting both operations must override all threee
+course, the objects supporting both operations must override all three
methods.
\wxheading{Derived from}
\func{bool}{CloseDocuments}{\param{bool }{force = TRUE}}
-Closes all currentled opened documents.
+Closes all currently opened documents.
\membersection{wxDocManager::CreateDocument}
\func{bool}{Init}{\param{wxFontEncoding }{input\_enc}, \param{wxFontEncoding }{output\_enc}, \param{int }{method = wxCONVERT\_STRICT}}
-Initialize convertion. Both output or input encoding may
+Initialize conversion. Both output or input encoding may
be wxFONTENCODING\_UNICODE, but only if wxUSE\_ENCODING is set to 1.
All subsequent calls to \helpref{Convert()}{wxencodingconverterconvert}
will interpret its argument
\item wxPLATFORM\_CURRENT
\end{itemize}
-wxPLATFORM\_CURRENT means the plaform this binary was compiled for.
+wxPLATFORM\_CURRENT means the platform this binary was compiled for.
Examples:
\wxheading{Data structures}
-Flages used by
+Flags used by
\helpref{wxFindReplaceData::GetFlags()}{wxfindreplacedatagetflags} and
\helpref{wxFindDialogEvent::GetFlags()}{wxfinddialogeventgetflags}:
\func{bool}{Seek}{\param{long }{ofs}, \param{wxSeekMode }{mode = wxFromStart}}
-Seeks to the specified position and returs TRUE on success.
+Seeks to the specified position and returns TRUE on success.
\wxheading{Parameters}
class.
{\bf Warning:} Under all non-Windows platforms this class is currently
-"input-only", i.e. you can receieve the files from another application, but
+"input-only", i.e. you can receive the files from another application, but
copying (or dragging) file(s) from a wxWindows application is not currently
supported.
wxFileName currently supports the file names in the Unix, DOS/Windows, Mac OS
and VMS formats. Although these formats are quite different, wxFileName tries
-to treat them all in the sam generic way. It supposes that all file names
+to treat them all in the same generic way. It supposes that all file names
consist of the following parts: the volume (also known as drive under Windows
or device under VMS), the path which is a sequence of directory names separated
by the \helpref{path separators}{wxfilenamegetpathseparators} and the full
\func{}{wxFileName}{\param{const wxString\& }{fullpath}, \param{wxPathFormat }{format = wxPATH\_NATIVE}}
From a full filename: if it terminates with a '/', a directory path
-is contructed (the name will be empty), otherwise a file name and
+is constructed (the name will be empty), otherwise a file name and
extension are extracted from it
\func{}{wxFileName}{\param{const wxString\& }{path}, \param{const wxString\& }{name}, \param{wxPathFormat }{format = wxPATH\_NATIVE}}
\func{wxString}{FindFirst}{\param{const wxString\& }{wildcard}, \param{int }{flags = 0}}
Works like \helpref{wxFindFirstFile}{wxfindfirstfile}. Returns name of the first
-filename (withing filesystem's current path) that matches {\it wildcard}. {\it flags} may be one of
+filename (within filesystem's current path) that matches {\it wildcard}. {\it flags} may be one of
wxFILE (only files), wxDIR (only directories) or 0 (both).
\membersection{wxFileSystem::FindNext}\label{wxfilesystemfindnext}
\func{virtual wxString}{FindFirst}{\param{const wxString\& }{wildcard}, \param{int }{flags = 0}}
Works like \helpref{wxFindFirstFile}{wxfindfirstfile}. Returns name of the first
-filename (withing filesystem's current path) that matches {\it wildcard}. {\it flags} may be one of
+filename (within filesystem's current path) that matches {\it wildcard}. {\it flags} may be one of
wxFILE (only files), wxDIR (only directories) or 0 (both).
This method is only called if \helpref{CanOpen}{wxfilesystemhandlercanopen} returns TRUE.
the message, so, for example, an e-mail client program will have to pass them to
this program. Because wxFileType itself can not know about these parameters,
it uses MessageParameters class to query them. The default implementation only
-requiers the caller to provide the file name (always used by the program to be
+requires the caller to provide the file name (always used by the program to be
called - it must know which file to open) and the MIME type and supposes that
there are no other parameters. If you wish to supply additional parameters, you
must derive your own class from MessageParameters and override GetParamValue()
\func{static wxString}{ExpandCommand}{\param{const wxString\&}{ command}, \param{MessageParameters\&}{ params}}
-This function is primarly intended for GetOpenCommand and GetPrintCommand
+This function is primarily intended for GetOpenCommand and GetPrintCommand
usage but may be also used by the application directly if, for example, you want
to use some non default command to open the file.
\twocolwidtha{7cm}
\begin{twocollist}\itemsep=0pt
-\twocolitem{format specificator}{with}
+\twocolitem{format specification}{with}
\twocolitem{\%s}{the full file name}
\twocolitem{\%t}{the MIME type}
\twocolitem{\%\{param\}}{the value of the parameter {\it param}}
\section{\class{wxFilterInputStream}}\label{wxfilterinputstream}
A filter stream has the capability of a normal stream but it can be placed on top
-of another stream. So, for example, it can uncompress or uncrypt the data which are read
+of another stream. So, for example, it can uncompress or decrypt the data which are read
from another stream and pass it to the requester.
\wxheading{Derived from}
say, KOI8 to create all fonts by default with KOI8 encoding. Initially, the
default application encoding is the same as default system encoding.}
\twocolitem{{\bf wxFONTENCODING\_ISO8859\_1...15}}{ISO8859 encodings.}
-\twocolitem{{\bf wxFONTENCODING\_KOI8}}{The standard russian encoding for Internet.}
+\twocolitem{{\bf wxFONTENCODING\_KOI8}}{The standard Russian encoding for Internet.}
\twocolitem{{\bf wxFONTENCODING\_CP1250...1252}}{Windows encodings similar to ISO8859 (but not identical).}
\end{twocollist}
If the specified encoding isn't available, no font is created.
\wxheading{Remarks}
If the desired font does not exist, the closest match will be chosen.
-Under Windows, only scaleable TrueType fonts are used.
+Under Windows, only scalable TrueType fonts are used.
See also \helpref{wxDC::SetFont}{wxdcsetfont}, \helpref{wxDC::DrawText}{wxdcdrawtext}
and \helpref{wxDC::GetTextExtent}{wxdcgettextextent}.
\func{void}{operator $=$}{\param{const wxFontData\&}{ data}}
-Assingment operator for the font data.
+Assignment operator for the font data.
\section{\class{wxFontDialog}}\label{wxfontdialog}
\wxheading{Parameters}
-\docparam{izonize}{If TRUE, iconizes the frame; if FALSE, shows and restores it.}
+\docparam{iconize}{If TRUE, iconizes the frame; if FALSE, shows and restores it.}
\wxheading{See also}
\twocolitem{{\bf wxMemoryFSHandler}}{This handler allows you to access
data stored in memory (such as bitmaps) as if they were regular files.
See \helpref{wxMemoryFSHandler documentation}{wxmemoryfshandler} for details.
-Include file is <wx/fs\_mem.h>. UURL is prefixed with memory:, e.g.
+Include file is <wx/fs\_mem.h>. URL is prefixed with memory:, e.g.
"memory:myfile.htm"}
\end{twocollist}
It provides more information than wxWindow's input stream
(stream, filename, mime type, anchor).
-{\bf Note:} Any pointer returned by wxFSFile's member is valid
-only as long as wxFSFile object exists. For example a call to GetStream()
+{\bf Note:} Any pointer returned by a method of wxFSFile is valid
+only as long as the wxFSFile object exists. For example a call to GetStream()
doesn't {\it create} the stream but only returns the pointer to it. In
other words after 10 calls to GetStream() you will obtain ten identical
pointers.
For asynchronous execution, however, the return value is the process id and
zero value indicates that the command could not be executed. As an added
-complication, the return value of $-1$ in this case indicattes that we didn't
+complication, the return value of $-1$ in this case indicates that we didn't
launch a new process, but connected to the running one (this can only happen in
case of using DDE under Windows for command execution). In particular, in this,
and only this, case the calling code will not get the notification about
\func{int}{wxKill}{\param{long}{ pid}, \param{int}{ sig = wxSIGTERM}, \param{wxKillError }{*rc = NULL}}
Equivalent to the Unix kill function: send the given signal {\it sig} to the
-process with PID {\it pid}. The valud signal values are
+process with PID {\it pid}. The valid signal values are
\begin{verbatim}
enum wxSignal
Copies {\it file1} to {\it file2}, returning TRUE if successful. If
{\it overwrite} parameter is TRUE (default), the destination file is overwritten
-if it exists, but if {\it overwrite} is FALSE, the functions failes in this
+if it exists, but if {\it overwrite} is FALSE, the functions fails in this
case.
\membersection{::wxGetCwd}\label{wxgetcwd}
wxWindows uses its own RTTI ("run-time type identification") system which
predates the current standard C++ RTTI and so is kept for backwards
-compatribility reasons but also because it allows some things which the
+compatibility reasons but also because it allows some things which the
standard RTTI doesn't directly support (such as creating a class from its
name).
\func{wxString}{GetColLabelValue}{\param{int }{col}}
-Returns the specifed column label. The default grid table class provides column labels of
+Returns the specified column label. The default grid table class provides column labels of
the form A,B...Z,AA,AB...ZZ,AAA... If you are using a custom grid table you can override
\helpref{wxGridTableBase::GetColLabelValue}{wxgridtablebasegetcollabelvalue} to provide
your own labels.
\func{bool}{GridLinesEnabled}{\void}
-Returnes TRUE if drawing of grid lines is turned on, FALSE otherwise.
+Returns TRUE if drawing of grid lines is turned on, FALSE otherwise.
\membersection{wxGrid::GetLabelBackgroundColour}\label{wxgridgetlabelbackgroundcolour}
\func{wxString}{GetRowLabelValue}{\param{int }{row}}
-Returns the specifed row label. The default grid table class provides numeric row labels.
+Returns the specified row label. The default grid table class provides numeric row labels.
If you are using a custom grid table you can override
\helpref{wxGridTableBase::GetRowLabelValue}{wxgridtablebasegetcollabelvalue} to provide
your own labels.
\func{void}{SetCellAlignment}{\param{int }{align}}
-Sets the horizontal and vertial alignment for grid cell text at the specified location.
+Sets the horizontal and vertical alignment for grid cell text at the specified location.
Horizontal alignment should be one of wxALIGN\_LEFT, wxALIGN\_CENTRE or wxALIGN\_RIGHT. \\
Vertical alignment should be one of wxALIGN\_TOP, wxALIGN\_CENTRE or wxALIGN\_BOTTOM.
\func{void}{SetDefaultCellAlignment}{\param{int }{horiz}, \param{int }{vert}}
-Sets the default horizontal and vertial alignment for grid cell text.
+Sets the default horizontal and vertical alignment for grid cell text.
Horizontal alignment should be one of wxALIGN\_LEFT, wxALIGN\_CENTRE or wxALIGN\_RIGHT.
\func{int}{GetRow}{\void}
-Row at which the evnet occurred.
+Row at which the event occurred.
\membersection{wxGridEvent::MetaDown}\label{wxgrideventmetadown}
\func{int}{GetLeftCol}{\void}
-Left column of the rectangualr area that was (de)selected.
+Left column of the rectangular area that was (de)selected.
\membersection{wxGridRangeSelectEvent::GetRightCol}\label{wxgridrangeselecteventgetrightcol}
\func{wxGridCellCoords}{GetTopLeftCoords}{\void}
-Top left corner of the rectangular area that was (de)delected.
+Top left corner of the rectangular area that was (de)selected.
\membersection{wxGridRangeSelectEvent::GetTopRow}\label{wxgridrangeselecteventgettoprow}
h2["Bill"] = "ABC";
wxString tmp = h2["Bill"];
// since element with key "Joe" is not present, this will return
- // the devault value, that is an empty string in the case of wxString
+ // the default value, that is an empty string in the case of wxString
MyClass tmp2 = h2["Joe"];
// iterate over all the elements in the class
browser).
\end{itemize}
-The remaining help controller classess need to be named
+The remaining help controller classes need to be named
explicitly by an application that wishes to make use of them.
There are currently the following help controller classes defined:
\item wxWinHelpController, for controlling Windows Help.
\item wxCHMHelpController, for controlling MS HTML Help. To use this, you need to set wxUSE\_MS\_HTML\_HELP
to 1 in setup.h and have htmlhelp.h header from Microsoft's HTML Help kit (you don't need
-VC++ specific htmlhelp.lib because wxWindows loads neccessary DLL at runtime and so it
+VC++ specific htmlhelp.lib because wxWindows loads necessary DLL at runtime and so it
works with all compilers).
\item wxBestHelpController, for controlling MS HTML Help or, if Microsoft's runtime is
not available, \helpref{wxHtmlHelpController}{wxhtmlhelpcontroller}. You need to provide
\func{void}{SetLink}{\param{const wxHtmlLinkInfo\& }{link}}
-Sets the hypertext link asocciated with this cell. (Default value
+Sets the hypertext link associated with this cell. (Default value
is \helpref{wxHtmlLinkInfo}{wxhtmllinkinfo}("", "") (no link))
\membersection{wxHtmlCell::SetNext}\label{wxhtmlcellsetnext}
\wxheading{Parameters}
-\docparam{maxwidth}{width of the area (on this DC) that is equivalent to screen's width,
+\docparam{maxwidth}{width of the area (on this DC) that is equivalent to the screen's width,
in pixels (you should set it to page width minus margins).
{\bf Note:} In the current implementation
(the latter stands for "HTML book"). In other words, {\tt AddBook("help.zip")} is possible and, in fact,
recommended way.
-If {\it show\_wait\_msg} is TRUE then a decorationless window with progress message is displayed.
+If {\it show\_wait\_msg} is TRUE then a decoration-less window with progress message is displayed.
\membersection{wxHtmlHelpController::CreateHelpFrame}\label{wxhtmlhelpcontrollercreatehelpframe}
\section{\class{wxHtmlLinkInfo}}\label{wxhtmllinkinfo}
-This class stores all neccessary information about hypertext
+This class stores all necessary information about hypertext
links (as represented by {\tt <A>} tag in HTML documents). In
current implementation it stores URL and target frame name.
{\it Note that frames are not currently supported by wxHTML!}
{\it sub-container} of the old one. (If you want to create a new container with
the same depth level you can call {\tt CloseContainer(); OpenContainer();}.)
-Use \helpref{CloseContaier}{wxhtmlwinparserclosecontainer} to close the
+Use \helpref{CloseContainer}{wxhtmlwinparserclosecontainer} to close the
container. This doesn't create a new container with same depth level but
it returns "control" to the parent container.
This class handles the {\bf generic} parsing of HTML document: it scans
the document and divide it into blocks of tags (where one block
-consists of begining and ending tag and of text between these
+consists of beginning and ending tag and of text between these
two tags).
It is independent from wxHtmlWindow and can be used as stand-alone parser
see InetGet sample for example).
It uses system of tag handlers to parse the HTML document. Tag handlers
-are not staticaly shared by all instances but are created for each
+are not statically shared by all instances but are created for each
wxHtmlParser instance. The reason is that the handler may contain
document-specific temporary data used during parsing (e.g. complicated
structures like tables).
\func{void}{AddTag}{\param{const wxHtmlTag\& }{tag}}
-This may (and may not) be overwriten in derived class.
+This may (and may not) be overwritten in derived class.
This method is called each time new tag is about to be added.
{\it tag} contains information about the tag. (See \helpref{wxHtmlTag}{wxhtmltag}
\func{virtual void}{AddWord}{\param{const char* }{txt}}
-Must be overwriten in derived class.
+Must be overwritten in derived class.
This method is called by \helpref{DoParsing}{wxhtmlparserdoparsing}
each time a part of text is parsed. {\it txt} is NOT only one word, it is
Opens given URL and returns {\tt wxFSFile} object that can be used to read data
from it. This method may return NULL in one of two cases: either the URL doesn't
-point to any valid resource or the URL is blocked by overriden implementation
+point to any valid resource or the URL is blocked by overridden implementation
of {\it OpenURL} in derived class.
\wxheading{Parameters}
\func{void}{SetMargins}{\param{float }{top = 25.2}, \param{float }{bottom = 25.2}, \param{float }{left = 25.2}, \param{float }{right = 25.2}, \param{float }{spaces = 5}}
-Sets margins in milimeters. Defaults to 1 inch for margins and 0.5cm for space
+Sets margins in millimeters. Defaults to 1 inch for margins and 0.5cm for space
between text and header and/or footer
See explanation (returned position is marked with `|'):
\begin{verbatim}
-bla bla bla <MYTAG> bla bla intenal text</MYTAG> bla bla
+bla bla bla <MYTAG> bla bla internal text</MYTAG> bla bla
|
\end{verbatim}
See explanation (returned position is marked with `|'):
\begin{verbatim}
-bla bla bla <MYTAG> bla bla intenal text</MYTAG> bla bla
+bla bla bla <MYTAG> bla bla internal text</MYTAG> bla bla
|
\end{verbatim}
See explanation (returned position is marked with `|'):
\begin{verbatim}
-bla bla bla <MYTAG> bla bla intenal text</MYTAG> bla bla
+bla bla bla <MYTAG> bla bla internal text</MYTAG> bla bla
|
\end{verbatim}
\constfunc{bool}{HasParam}{\param{const wxString\& }{par}}
-Returns TRUE if the tag has parameter of the given name.
+Returns TRUE if the tag has a parameter of the given name.
Example : {\tt <FONT SIZE=+2 COLOR="\#FF00FF">} has two parameters named
"SIZE" and "COLOR".
\constfunc{wxString}{ScanParam}{\param{const wxString\& }{par}, \param{const wxChar *}{format}, \param{void *}{value}}
-This method scans given parameter. Usage is exactly the same as sscanf's
-usage except that you don't pass string but parameter name as the first parameter
-and that you can only retrieve one value (i.e. you can use only one "\%" element
+This method scans the given parameter. Usage is exactly the same as sscanf's
+usage except that you don't pass a string but a parameter name as the first
+argument
+and you can only retrieve one value (i.e. you can use only one "\%" element
in {\it format}).
\wxheading{Parameters}
-\docparam{par}{The name of tag you want to query}
+\docparam{par}{The name of the tag you want to query}
\docparam{format}{scanf()-like format string.}
-\docparam{value}{pointer to a variable to store value in }
+\docparam{value}{pointer to a variable to store the value in }
\func{virtual bool}{HandleTag}{\param{const wxHtmlTag\& }{tag}}
This is the core method of each handler. It is called each time
-one of supported tags is detected. {\it tag} contains all neccessary
+one of supported tags is detected. {\it tag} contains all necessary
info (see \helpref{wxHtmlTag}{wxhtmltag} for details).
\wxheading{Return value}
}
\end{verbatim}
-You shouldn't call ParseInner if the tag is not paired with ending one.
+You shouldn't call ParseInner if the tag is not paired with an ending one.
\membersection{wxHtmlTagHandler::ParseInner}\label{wxhtmltaghandlerparseinner}
\func{void}{ParseInner}{\param{const wxHtmlTag\& }{tag}}
This method calls parser's \helpref{DoParsing}{wxhtmlparserdoparsing} method
-for the string between this tag and paired ending tag:
+for the string between this tag and the paired ending tag:
\begin{verbatim}
...<A HREF="x.htm">Hello, world!</A>...
\section{\class{wxHtmlTagsModule}}\label{wxhtmltagsmodule}
This class provides easy way of filling wxHtmlWinParser's table of
-tag handlers. It is used almost exclusively together with set of
+tag handlers. It is used almost exclusively together with the set of
\helpref{TAGS\_MODULE\_* macros}{handlers}
\wxheading{Derived from}
\func{virtual void}{FillHandlersTable}{\param{wxHtmlWinParser }{*parser}}
-You must override this method. In most common case it is body consists
-only of lines of following type:
+You must override this method. In most common case its body consists
+only of lines of the following type:
\begin{verbatim}
parser -> AddTagHandler(new MyHandler);
\end{verbatim}
-I recommend using {\bf TAGS\_MODULE\_*} macros.
+I recommend using the {\bf TAGS\_MODULE\_*} macros.
\wxheading{Paremeters}
\wxheading{Note}
You can know the size of the file you are getting using \helpref{wxStreamBase::GetSize()}{wxstreambasegetsize}.
-But there is a limitation: as HTTP servers aren't obliged to pass the size ofi
+But there is a limitation: as HTTP servers aren't obliged to pass the size of
the file, in some case, you will be returned 0xfffffff by GetSize(). In these
cases, you should use the value returned by \helpref{wxInputStream::LastRead()}{wxinputstreamlastread}:
this value will be 0 when the stream is finished.
\wxheading{Parameters}
\docparam{normal\_face}{This is face name for normal (i.e. non-fixed) font.
-It can be either empty string (then the default face is choosen) or
+It can be either empty string (then the default face is chosen) or
platform-specific face name. Examples are "helvetica" under Unix or
"Times New Roman" under Windows.}
SetFonts("", "", {7, 8, 10, 12, 16, 22, 30});
\end{verbatim}
-Athough it seems different the fact is that the fonts are of approximately
+Although it seems different the fact is that the fonts are of approximately
same size under both platforms (due to wxMSW / wxGTK inconsistency)
\membersection{wxHtmlWindow::SetPage}\label{wxhtmlwindowsetpage}
\func{}{wxHtmlWinParser}{\param{wxHtmlWindow }{*wnd}}
Constructor. Don't use the default one, use constructor with
-{\it wnd} paremeter ({\it wnd} is pointer to associated \helpref{wxHtmlWindow}{wxhtmlwindow})
+{\it wnd} parameter ({\it wnd} is pointer to associated \helpref{wxHtmlWindow}{wxhtmlwindow})
\membersection{wxHtmlWinParser::AddModule}\label{wxhtmlwinparseraddmodule}
\constfunc{wxHtmlContainerCell*}{GetContainer}{\void}
-Returns pointer to the currectly opened container (see \helpref{Overview}{cells}).
+Returns pointer to the currently opened container (see \helpref{Overview}{cells}).
Common use:
\begin{verbatim}
\section{wxWindows Hello World sample}\label{helloworld}
As many people have requested a mini-sample to be published here
-so that some quick judgments concerning syntax
+so that some quick judgment concerning syntax
and basic principles can be made, you can now look at wxWindows'
"Hello World":
\wxheading{Available image handlers}
The following image handlers are available. {\bf wxBMPHandler} is always
-installed by default. To use other image formats, install the appropiate
+installed by default. To use other image formats, install the appropriate
handler with \helpref{wxImage::AddHandler}{wximageaddhandler} or
\helpref{wxInitAllImageHandlers}{wxinitallimagehandlers}.
Returns the image data as an array. This is most often used when doing
direct image manipulation. The return value points to an array of
-chararcters in RGBGBRGB... format.
+characters in RGBGBRGB... format.
\membersection{wxImage::GetGreen}\label{wximagegetgreen}
\twocolitem{{\bf wxIMAGELIST\_DRAW\_NORMAL}}{Draw the image normally.}
\twocolitem{{\bf wxIMAGELIST\_DRAW\_TRANSPARENT}}{Draw the image with transparency.}
\twocolitem{{\bf wxIMAGELIST\_DRAW\_SELECTED}}{Draw the image in selected state.}
-\twocolitem{{\bf wxIMAGELIST\_DRAW\_FOCUSED}}{Draw the image in a focussed state.}
+\twocolitem{{\bf wxIMAGELIST\_DRAW\_FOCUSED}}{Draw the image in a focused state.}
\end{twocollist}
}
\func{size\_t}{Ungetch}{\param{const char*}{ buffer}, \param{size\_t}{ size}}
This function is only useful in {\it read} mode. It is the manager of the "Write-Back"
-buffer. This buffer acts like a temporary buffer where datas which has to be
+buffer. This buffer acts like a temporary buffer where data which has to be
read during the next read IO call are put. This is useful when you get a big
block of data which you didn't want to read: you can replace them at the top
of the input queue by this way.
{\bf Note for Windows programmers:} The key and char events in wxWindows are
similar to but slightly different from Windows {\tt WM\_KEYDOWN} and
{\tt WM\_CHAR} events. In particular, Alt-x combination will generate a char
-event in wxWindows (unless it is used as an acclerator).
+event in wxWindows (unless it is used as an accelerator).
{\bf Tip:} be sure to call {\tt event.Skip()} for events that you don't process in
key event function, otherwise menu shortcuts may cease to work under Windows.
Say you wish to have an extra toolbar at the top of the frame, a project window to the left of
the MDI client window, and an output window above the status bar. You should therefore create
the windows in this order: toolbar, output window, project window. This ensures that the toolbar and
-output window take up space at the top and bottom, and then the remaining height inbetween is used for
+output window take up space at the top and bottom, and then the remaining height in-between is used for
the project window.
wxLayoutAlgorithm is quite independent of the way in which
...
- // the only requirment for the rest is to be AFTER the full declaration of
+ // the only requirement for the rest is to be AFTER the full declaration of
// MyListElement (for WX_DECLARE_LIST forward declaration is enough), but
// usually it will be found in the source file and not in the header
\twocolitem{{\bf EVT\_LISTBOX(id, func)}}{Process a wxEVT\_COMMAND\_LISTBOX\_SELECTED event,
when an item on the list is selected.}
\twocolitem{{\bf EVT\_LISTBOX\_DCLICK(id, func)}}{Process a wxEVT\_COMMAND\_LISTBOX\_DOUBLECLICKED event,
-when the listbox is doubleclicked.}
+when the listbox is double-clicked.}
\end{twocollist}
\wxheading{See also}
\pythonnote{The wxPython version of this method takes no parameters
and returns a tuple of the selected items.}
-\perlnote{In wxPerl this method takes no parameters and returna the
+\perlnote{In wxPerl this method takes no parameters and return the
selected items as a list.}
\membersection{wxListBox::GetString}\label{wxlistboxgetstring}
ID and code and returns the wxRect.}
\perlnote{In wxPerl this method takes only the {\bf item} parameter and
-retutrns a Wx::Rect ( or undef ).}
+returns a Wx::Rect ( or undef ).}
\membersection{wxListCtrl::GetItemSpacing}\label{wxlistctrlgetitemspacing}
\constfunc{long}{GetNextItem}{\param{long }{item}, \param{int }{geometry = wxLIST\_NEXT\_ALL}, \param{int }{state = wxLIST\_STATE\_DONTCARE}}
-Searches for an item with the given goemetry or state, starting from
+Searches for an item with the given geometry or state, starting from
{\it item} but excluding the {\it item} itself. If {\it item} is -1,
the first item that matches the specified flags will be returned.
This method can only be used with virtual list controls. It is used to indicate
to the control the number of items it contains. After calling it, the main
program should be ready to handle calls to various item callbacks (such as
-\helpref{OnGetItemText}{wxlistctrlongetitemtext}) for all vitems in the range
+\helpref{OnGetItemText}{wxlistctrlongetitemtext}) for all items in the range
from $0$ to {\it count}.
\membersection{wxListCtrl::SetItemData}\label{wxlistctrlsetitemdata}
\func{static void}{AddLanguage}{\param{const wxLanguageInfo\& }{info}}
Adds custom, user-defined language to the database of known languages. This
-database is used in conjuction with the first form of
+database is used in conjunction with the first form of
\helpref{Init}{wxlocaleinit}.
wxLanguageInfo is defined as follows:
Finally, the {\it wxLog::DoLog()} function automatically prepends a time stamp
to all the messages. The format of the time stamp may be changed: it can be
-any string with \% specificators fully described in the documentation of the
+any string with \% specifications fully described in the documentation of the
standard {\it strftime()} function. For example, the default format is
"[\%d/\%b/\%y \%H:\%M:\%S] " which gives something like "[17/Sep/98 22:10:16] "
(without quotes) for the current date. Setting an empty string as the time
\func{static void}{SetVerbose}{\param{bool }{ verbose = TRUE}}
-Activates or desactivates verbose mode in which the verbose messages are
+Activates or deactivates verbose mode in which the verbose messages are
logged as the normal ones instead of being silently dropped.
\membersection{wxLog::GetVerbose}\label{wxloggetverbose}
working with 64 bit integers independently of the architecture.
wxLongLong defines all usual arithmetic operations such as addition,
-substraction, bitwise shifts and logical operations as well as multiplication
+subtraction, bitwise shifts and logical operations as well as multiplication
and division (not yet for the machines without native {\it long long}). It
also has operators for implicit construction from and conversion to the native
{\it long long} type if it exists and {\it long}.
\constfunc{long}{GetHi}{\void}
-Returnes the high 32 bits of 64 bit integer.
+Returns the high 32 bits of 64 bit integer.
\membersection{wxLongLong::GetLo}\label{wxlonglonggetlo}
\constfunc{unsigned long}{GetLo}{\void}
-Returnes the low 32 bits of 64 bit integer.
+Returns the low 32 bits of 64 bit integer.
\membersection{wxLongLong::GetValue}\label{wxlonglonggetvalue}
\item Null bytes do not occur in the encoding, except when there's an actual Unicode
null character
\item Preserves sort ordering for plain 8-bit comparison routines like strcmp()
-\item High bit patterns unambiguates character boundaries, and makes it easy to
+\item High bit patterns disambiguates character boundaries, and makes it easy to
detect whether a string is encoded with UTF-8 or not
\end{itemize}
Constructs a new memory device context.
Use the {\it Ok} member to test whether the constructor was successful
-in creating a useable device context. Don't forget to select a bitmap
+in creating a usable device context. Don't forget to select a bitmap
into the DC before drawing on it.
\membersection{wxMemoryDC::SelectObject}
Menu items may be either normal items, check items or radio items. Normal items
don't have any special properties while the check items have a boolean flag
associated to them and they show a checkmark in the menu when the flag is set.
-wxWindows automatically togles the flag value when the item is clicked and its
+wxWindows automatically toggles the flag value when the item is clicked and its
value may be retrieved using either \helpref{IsChecked}{wxmenuischecked} method
of wxMenu or wxMenuBar itself or by using
\helpref{wxEvent::IsChecked}{wxcommandeventischecked} when you get the menu
\pythonnote{Only the default constructor is supported in wxPython.
Use wxMenuBar.Append instead.}
-\perlnote{wxPerl only supports the first contructor:
+\perlnote{wxPerl only supports the first constructor:
use {\tt Append} instead.}
\membersection{wxMenuBar::\destruct{wxMenuBar}}
\constfunc{wxString}{GetHelpString}{\param{int}{ id}}
-Gets the help string associated with the menu item identifer.
+Gets the help string associated with the menu item identifier.
\wxheading{Parameters}
\twocolitem{{\bf EVT\_MENU\_OPEN(func)}}{A menu is about to be opened.}
\twocolitem{{\bf EVT\_MENU\_CLOSE(func)}}{A menu has been just closed.}
\twocolitem{{\bf EVT\_MENU\_HIGHLIGHT(id, func)}}{The menu item with the
-speicifed id has been highlighted: used to show help prompts in the status bar
+specified id has been highlighted: used to show help prompts in the status bar
by \helpref{wxFrame}{wxframe}}
\twocolitem{{\bf EVT\_MENU\_HIGHLIGHT\_ALL(func)}}{A menu item has been
highlighted, i.e. the currently selected menu item has changed.}
\constfunc{wxString}{GetLabel}{\void}
Returns the text associated with the menu item without any accelerator
-characaters it might contain.
+characters it might contain.
\wxheading{See also}
\func{static wxString}{GetLabelFromText}{\param{const wxString\& }{text}}
-Strips all accelerator characeters and mnemonics from the given {\it text}.
+Strips all accelerator characters and mnemonics from the given {\it text}.
For example,
\begin{verbatim}
used for anything, but the wxMetafile object must still be destroyed by
the application.
-Below is a example of metafle, metafile device context and clipboard use
+Below is a example of metafile, metafile device context and clipboard use
from the {\tt hello.cpp} example. Note the way the metafile dimensions
are passed to the clipboard, making use of the device context's ability
to keep track of the maximum extent of drawing commands.
\func{void}{AddFallbacks}{\param{const wxFileTypeInfo *}{fallbacks}}
-This function may be used to provdie hard-wired fallbacks for the MIME types
+This function may be used to provide hard-wired fallbacks for the MIME types
and extensions that might not be present in the system MIME database.
% TODO
{\it wildcard} is '*'. Note that the '*' wildcard is not allowed in
{\it mimeType} itself.
-The comparaison don by this function is case insensitive so it is not
+The comparison don by this function is case insensitive so it is not
necessary to convert the strings to the same case before calling it.
\membersection{wxMimeTypesManager::ReadMailcap}\label{wxmimetypesmanagerreadmailcap}
\func{}{\destruct{wxMutexLocker}}{\void}
-Destuctor releases the mutex if it was successfully acquired in the ctor.
+Destructor releases the mutex if it was successfully acquired in the ctor.
\membersection{wxMutexLocker::IsOk}\label{wxmutexlockerisok}
been measured by machines, i.e. that may have thousands of values. One example of
such data would be the well known ECG measuring the electrical activity of your
heart: the measuring device will produce thousands of values per minute, several
-measurements are done simultanously and you might want to have a look at parts
+measurements are done simultaneously and you might want to have a look at parts
of the curves, enlarging them or scrolling from one position to another. Note
that this window is not useful for real-time measuring or for displaying charts
with error bars etc.
\wxheading{Window styles}
\begin{twocollist}\itemsep=0pt
-\twocolitem{\windowstyle{wxPLOT\_BUTTON\_MOVE}}{Display buttons to allao moving individual curves up or down.}
+\twocolitem{\windowstyle{wxPLOT\_BUTTON\_MOVE}}{Display buttons to allow moving individual curves up or down.}
\twocolitem{\windowstyle{wxPLOT\_BUTTON\_ENLARGE}}{Display buttons to allow enlarging individual curves vertically.}
\twocolitem{\windowstyle{wxPLOT\_BUTTON\_ZOOM}}{Display buttons to allow zooming all curves horizontally.}
\twocolitem{\windowstyle{wxPLOT\_BUTTON\_ALL}}{Display all buttons.}
\func{void}{SetUnitsPerValue}{\param{double }{upv}}
-This sets the virtual untis per value. Normally, you will not be interested in
+This sets the virtual units per value. Normally, you will not be interested in
what measured value you see, but what it stands for. If you want to display seconds
on the X axis and the measuring device produced 50 values per second, set this
value to 50. This will affect all curves being displayed.
various parameters. {\it parent} is the parent of the printer dialog box.
Use the {\it Ok} member to test whether the constructor was successful
-in creating a useable device context.
+in creating a usable device context.
See \helpref{Printer settings}{printersettings} for functions to set and
get PostScript printing settings.
displayed. {\it device} indicates the type of printer and {\it output}
is an optional file for printing to. The {\it driver} parameter is
currently unused. Use the {\it Ok} member to test whether the
-constructor was successful in creating a useable device context.
+constructor was successful in creating a usable device context.
This constructor is deprecated and retained only for backward compatibility.
\func{}{wxPrintout}{\param{const wxString\& }{title = "Printout"}}
-Constructor. Pass an optional title argument - the curent filename would be a good idea. This will appear in the printing list
+Constructor. Pass an optional title argument - the current filename would be a good idea. This will appear in the printing list
(at least in MSW)
\membersection{wxPrintout::\destruct{wxPrintout}}
\helpref{GetInputStream}{wxprocessgetinputstream},
\helpref{GetOutputStream}{wxprocessgetoutputstream} and
\helpref{GetErrorStream}{wxprocessgeterrorstream} can then be used to retrieve
-the streams corresponding to the child process stdandard output, input and
+the streams corresponding to the child process standard output, input and
error output respectively.
\perlnote{In wxPerl this class has an additional {\tt Destroy} method,
Finds the appropriate validator and unloads the property from the controls, by calling
wxPropertyListView::RetrieveProperty, wxPropertyValidator::OnClearControls and (if we're in
-detailed editing mdoe) wxPropertyValidator::OnClearDetailControls.
+detailed editing mode) wxPropertyValidator::OnClearDetailControls.
\membersection{wxPropertyListView::GetPanel}\label{wxpropertylistviewgetpanel}
\func{wxInputStream *}{GetInputStream}{\param{const wxString\&}{ path}}
Creates a new input stream on the the specified path. You can use all but seek
-functionnality of wxStream. Seek isn't available on all stream. For example,
+functionality of wxStream. Seek isn't available on all stream. For example,
http or ftp streams doesn't deal with it. Other functions like StreamSize and
Tell aren't available for the moment for this sort of stream.
You will be notified when the EOF is reached by an error.
\func{void}{SetId}{\param{const wxString\& }{id}}
-Yu have to override OnDrop to get at the data.
+You have to override OnDrop to get at the data.
The string ID identifies the format of clipboard or DnD data. A word
-rocessor would e.g. add a wxTextDataObject and a wxPrivateDataObject
+processor would e.g. add a wxTextDataObject and a wxPrivateDataObject
to the clipboard - the latter with the Id "WXWORD\_FORMAT".
\membersection{wxPrivateDropTarget::GetId}\label{wxprivatedroptargetgetid}
\def\@mpty{}
\def\s@tsize#1 #2 #3 #4\@ndsize{
\def\psllx{#1}\def\pslly{#2}%
- \def\psurx{#3}\def\psury{#4}% needed by a crazyness of dvips!
+ \def\psurx{#3}\def\psury{#4}% needed by a craziness of dvips!
\ifx\psurx\@mpty\NotB@undingBoxtrue% this is not a valid one!
\else
\drawinght=#4bp\advance\drawinght by-#2bp
%
% \textleftof\anybox: Sample text\endtext
% inserts "Sample text" on the left of \anybox ie \vbox, \psbox.
-% \textrightof is the symmetric (not documented, too uggly)
+% \textrightof is the symmetric (not documented, too ugly)
% Welcome any suggestion about clean wraparound macros from
% TeXhackers reading this
%
Increase the rectangle size by {\it dx} in x direction and {\it dy} in y
direction. Both (or one of) parameters may be negative to decrease the
-rectngle size.
+rectangle size.
The second form uses the same {\it diff} for both {\it dx} and {\it dy}.
synonym for it. Backslash may be used to quote itself or {\tt \&} character.
{\it maxMatches} may be used to limit the number of replacements made, setting
-it to $1$, for example, will only replace first occurence (if any) of the
+it to $1$, for example, will only replace first occurrence (if any) of the
pattern in the text while default value of $0$ means replace all.
\membersection{wxRegEx::ReplaceAll}\label{wxregexreplaceall}
\constfunc{int}{ReplaceAll}{\param{wxString* }{text}, \param{const wxString\& }{replacement}}
-Replace all occurences: this is actually a synonym for
+Replace all occurrences: this is actually a synonym for
\helpref{Replace()}{wxregexreplace}.
\wxheading{See also}
\constfunc{int}{ReplaceFirst}{\param{wxString* }{text}, \param{const wxString\& }{replacement}}
-Replace the first occurence.
+Replace the first occurrence.
\wxheading{See also}
\twocolitem{{\bf EVT\_SCROLLWIN\_PAGEUP(func)}}{Process wxEVT\_SCROLLWIN\_PAGEUP page up events.}
\twocolitem{{\bf EVT\_SCROLLWIN\_PAGEDOWN(func)}}{Process wxEVT\_SCROLLWIN\_PAGEDOWN page down events.}
\twocolitem{{\bf EVT\_SCROLLWIN\_THUMBTRACK(func)}}{Process wxEVT\_SCROLLWIN\_THUMBTRACK thumbtrack events (frequent events
-sent as the user drags the thumtrack).}
+sent as the user drags the thumbtrack).}
\twocolitem{{\bf EVT\_SCROLLWIN\_THUMBRELEASE(func)}}{Process wxEVT\_SCROLLWIN\_THUMBRELEASE thumb release events.}
\end{twocollist}%
\twocolitem{{\bf EVT\_SCROLL\_PAGEUP(func)}}{Process wxEVT\_SCROLL\_PAGEUP page up events.}
\twocolitem{{\bf EVT\_SCROLL\_PAGEDOWN(func)}}{Process wxEVT\_SCROLL\_PAGEDOWN page down events.}
\twocolitem{{\bf EVT\_SCROLL\_THUMBTRACK(func)}}{Process wxEVT\_SCROLL\_THUMBTRACK thumbtrack events (frequent events
-sent as the user drags the thumtrack).}
+sent as the user drags the thumbtrack).}
\twocolitem{{\bf EVT\_SCROLL\_THUMBRELEASE(func)}}{Process wxEVT\_SCROLL\_THUMBRELEASE thumb release events.}
\twocolitem{{\bf EVT\_COMMAND\_SCROLL(id, func)}}{Process all scroll events.}
\twocolitem{{\bf EVT\_COMMAND\_SCROLL\_TOP(id, func)}}{Process wxEVT\_SCROLL\_TOP scroll-to-top events.}
\twocolitem{{\bf EVT\_COMMAND\_SCROLL\_PAGEUP(id, func)}}{Process wxEVT\_SCROLL\_PAGEUP page up events.}
\twocolitem{{\bf EVT\_COMMAND\_SCROLL\_PAGEDOWN(id, func)}}{Process wxEVT\_SCROLL\_PAGEDOWN page down events.}
\twocolitem{{\bf EVT\_COMMAND\_SCROLL\_THUMBTRACK(id, func)}}{Process wxEVT\_SCROLL\_THUMBTRACK thumbtrack events (frequent events
-sent as the user drags the thumtrack).}
+sent as the user drags the thumbtrack).}
\twocolitem{{\bf EVT\_COMMAND\_SCROLL\_THUMBRELEASE(func)}}{Process wxEVT\_SCROLL\_THUMBRELEASE thumb release events.}
\end{twocollist}%
counter becomes strictly positive again as the result of calling
\helpref{Post}{wxsemaphorepost} which increments the counter.
-In general, the semaphores are useful to restict access to a shared resource
+In general, the semaphores are useful to restrict access to a shared resource
which can only be accessed by some fixed number of clients at once. For
example, when modeling a hotel reservation system a semaphore with the counter
equal to the total number of available rooms could be created. Each time a room
\func{bool}{Wait}{\param{unsigned long }{timeout\_millis}}
Same as the version above, but with a timeout limit: returns {\tt TRUE} if the
-semaphore was acquired and {\tt FALSE} if the timeout has ellapsed
+semaphore was acquired and {\tt FALSE} if the timeout has elapsed
\twocolitem{{\bf wxSYS\_COLOUR\_BTNTEXT}}{Text on push buttons.}
\twocolitem{{\bf wxSYS\_COLOUR\_INACTIVECAPTIONTEXT}}{Colour of text in active captions.}
\twocolitem{{\bf wxSYS\_COLOUR\_BTNHIGHLIGHT}}{Highlight colour for buttons (same as wxSYS\_COLOUR\_3DHILIGHT).}
-\twocolitem{{\bf wxSYS\_COLOUR\_3DDKSHADOW}}{Dark shadow for three-dimensional dispaly elements.}
+\twocolitem{{\bf wxSYS\_COLOUR\_3DDKSHADOW}}{Dark shadow for three-dimensional display elements.}
\twocolitem{{\bf wxSYS\_COLOUR\_3DLIGHT}}{Light colour for three-dimensional display elements.}
\twocolitem{{\bf wxSYS\_COLOUR\_INFOTEXT}}{Text colour for tooltip controls.}
\twocolitem{{\bf wxSYS\_COLOUR\_INFOBK}}{Background colour for tooltip controls.}
horizontal boxes on the level beneath).}
\docparam{width and height}{The dimension of a spacer to be added to the sizer. Adding spacers to sizers
-gives more flexilibilty in the design of dialogs; imagine for example a horizontal box with two buttons at the
+gives more flexibility in the design of dialogs; imagine for example a horizontal box with two buttons at the
bottom of a dialog: you might want to insert a space between the two buttons and make that space stretchable
using the {\it option} flag and the result will be that the left button will be aligned with the left
side of the dialog and the right button with the right side - the space in between will shrink and grow with
\docparam{option}{Although the meaning of this parameter is undefined in wxSizer, it is used in wxBoxSizer
to indicate if a child of a sizer can change its size in the main orientation of the wxBoxSizer - where
-0 stands for not changable and a value of more than zero is interpreted relative to the value of other
+0 stands for not changeable and a value of more than zero is interpreted relative to the value of other
children of the same wxBoxSizer. For example, you might have a horizontal wxBoxSizer with three children, two
of which are supposed to change their size with the sizer. Then the two stretchable windows would get a
value of 1 each to make them grow and shrink equally with the sizer's horizontal dimension.}
equivalent sizer and {\it nth} is the position of the child in the sizer, typically 0 for
the first item. This method does not cause any layout or resizing to take place and does
not delete the window itself. Call \helpref{wxSizer::Layout}{wxsizerlayout} to update
-the layout "on screen" after removing a child fom the sizer.
+the layout "on screen" after removing a child from the sizer.
Returns TRUE if the child item was found and removed, FALSE otherwise.
\func{void}{SetDimension}{\param{int }{x}, \param{int }{y}, \param{int }{width}, \param{int }{height}}
Call this to force the sizer to take the given dimension and thus force the items owned
-by the sizer to resize themselves according to the rules defined by the paramater in the
+by the sizer to resize themselves according to the rules defined by the parameter in the
\helpref{Add}{wxsizeradd} and \helpref{Prepend}{wxsizerprepend} methods.
\membersection{wxSizer::SetMinSize}\label{wxsizersetminsize}
Use \helpref{wxSingleChoiceDialog::ShowModal}{wxsinglechoicedialogshowmodal} to show the dialog.
-\pythonnote{For Python the two parametes {\tt n} and {\tt choices} are collapsed
+\pythonnote{For Python the two parameters {\tt n} and {\tt choices} are collapsed
into a single parameter {\tt choices} which is expected to be a Python
list of strings.}
{\bf wxSOCKET\_OUTPUT} event.
The {\bf wxSOCKET\_CONNECTION} event is issued when a delayed connection
-request completes succesfully (client) or when a new connection arrives
+request completes successfully (client) or when a new connection arrives
at the incoming queue (server).
The {\bf wxSOCKET\_LOST} event is issued when a close indication is
\func{void}{SetFlags}{\param{wxSocketFlags}{ flags}}
Use SetFlags to customize IO operation for this socket.
-The {\it flags} parameter may be a combination of flags ORed toghether.
+The {\it flags} parameter may be a combination of flags ORed together.
The following flags can be used:
\twocolwidtha{7cm}
\func{void}{SetNotify}{\param{wxSocketEventFlags}{ flags}}
SetNotify specifies which socket events are to be sent to the event handler.
-The {\it flags} parameter may be combination of flags ORed toghether. The
+The {\it flags} parameter may be combination of flags ORed together. The
following flags can be used:
\twocolwidtha{7cm}
\wxheading{Return value}
WaitOnConnect returns TRUE if the connection request completes. This
-does not necessarily mean that the connection was succesfully established;
+does not necessarily mean that the connection was successfully established;
it might also happen that the connection was refused by the peer. Use
\helpref{IsConnected}{wxsocketbaseisconnected} to distinguish between
these two situations.
This class represents the events generated by a splitter control. Also there is
only one event class, the data associated to the different events is not the
same and so not all accessor functions may be called for each event. The
-documentation mentions the kind of event(s) for which the given acessor
+documentation mentions the kind of event(s) for which the given accessor
function makes sense: calling it for other types of events will result
in assert failure (in debug mode) and will return meaningless results.
\begin{twocollist}\itemsep=0pt
\twocolitem{\windowstyle{wxALIGN\_LEFT}}{Align the text to the left}
\twocolitem{\windowstyle{wxALIGN\_RIGHT}}{Align the text to the right}
-\twocolitem{\windowstyle{wxALIGN\_CENTRE}}{Center the text (horisontally)}
+\twocolitem{\windowstyle{wxALIGN\_CENTRE}}{Center the text (horizontally)}
\twocolitem{\windowstyle{wxST\_NO\_AUTORESIZE}}{By default, the control will
adjust its size to exactly fit to the size of the text when
\helpref{SetLabel}{wxstatictextsetlabel} is called. If this style flag is
\pythonnote{Only the first parameter is accepted. Use SetStatusWidths
to set the widths of the fields.}
-\perlnote{In wxPerl this function acceps only the {\tt n} parameter.
+\perlnote{In wxPerl this function accepts only the {\tt n} parameter.
Use SetStatusWidths to set the field widths.}
\wxheading{Parameters}
\func{size\_t}{Write}{\param{const void *}{buffer}, \param{size\_t }{size}}
-Writes a block of the specified {\it size} using datas of {\it buffer}. The datas
+Writes a block of the specified {\it size} using data of {\it buffer}. The data
are cached in a buffer before being sent in one block to the stream.
\func{size\_t}{Write}{\param{wxStreamBuffer *}{buffer}}
\func{void}{Flushable}{\param{bool}{ flushable}}
-Toggles the flushable flag. If {\it flushable} is disabled, no datas are sent
+Toggles the flushable flag. If {\it flushable} is disabled, no data are sent
to the parent stream.
\membersection{wxStreamBuffer::FlushBuffer}
\func{size\_t}{GetDataLeft}{\void}
-Returns the amount of available datas in the buffer.
+Returns the amount of available data in the buffer.
% --------------
% Administration
There are 3 main classes declared in {\tt <wx/datetime.h>}: except
\helpref{wxDateTime}{wxdatetime} itself which represents an absolute
-moment in the time, there are also two classes -
+moment in time, there are also two classes -
\helpref{wxTimeSpan}{wxtimespan} and \helpref{wxDateSpan}{wxdatespan} which
represent the intervals of time.
First, there is the direct and self-explaining way implemented by
\helpref{wxTimeSpan}{wxtimespan}: it is just a difference in milliseconds
-between two moments in the time. Adding and substracting such interval to
+between two moments in time. Adding or subtracting such an interval to
wxDateTime is always well-defined and is a fast operation.
But in the daily life other, calendar-dependent time interval specifications are
the year is leap or not).
This is why there is another class for representing such intervals called
-\helpref{wxDateSpan}{wxdatespan}. It handles this sort of operations in the
-most natural way possible, but note that manipulating with thei ntervals of
+\helpref{wxDateSpan}{wxdatespan}. It handles these sort of operations in the
+most natural way possible, but note that manipulating with intervals of
this kind is not always well-defined. Consider, for example, Jan 31 + `1
month': this will give Feb 28 (or 29), i.e. the last day of February and not
-the non-existing Feb 31. Of course, this is what is usually wanted, but you
-still might be surprized to notice that now substracting back the same
+the non-existent Feb 31. Of course, this is what is usually wanted, but you
+still might be surprised to notice that now subtracting back the same
interval from Feb 28 will result in Jan 28 and {\bf not} Jan 31 we started
with!
So, unless you plan to implement some kind of natural language parsing in the
program, you should probably use wxTimeSpan instead of wxDateSpan (which is
also more efficient). However, wxDateSpan may be very useful in situations
-when you do need to understand what does `in a month' mean (of course, it is
+when you do need to understand what `in a month' means (of course, it is
just {\tt wxDateTime::Now() + wxDateSpan::Month()}).
\subsection{Date arithmetics}\label{tdatearithm}
Many different operations may be performed with the dates, however not all of
-them make sense. For example, multiplying date by a number is an invalid
-operation, even though multiplying either of time span classes by a number is
-perfectly valid.
+them make sense. For example, multiplying a date by a number is an invalid
+operation, even though multiplying either of the time span classes by a number
+is perfectly valid.
Here is what can be done:
\begin{twocollist}\itemsep=0pt
\twocolitem{{\bf Addition}}{a wxTimeSpan or wxDateSpan can be added to wxDateTime
resulting in a new wxDateTime object and also 2 objects of the same span class
-can be added together giving another object of the smae class.}
-\twocolitem{{\bf Substraction}}{the same types of operations as above are
+can be added together giving another object of the same class.}
+\twocolitem{{\bf Subtraction}}{the same types of operations as above are
allowed and, additionally, a difference between two wxDateTime objects can be
taken and this will yield wxTimeSpan.}
\twocolitem{{\bf Multiplication}}{a wxTimeSpan or wxDateSpan object can be
\end{twocollist}
For all these operations there are corresponding global (overloaded) operators
-and also member functions which are synonyms for them: Add(), Substract() and
+and also member functions which are synonyms for them: Add(), Subtract() and
Multiply(). Unary minus as well as composite assignment operations (like $+=$)
are only implemented as members and Neg() is the synonym for unary minus.
the most common case - when the date should be constructed in GMT.
You also can just retrieve the value for some time zone without converting the
-obejct to it first. For this you may pass TimeZone argument to any of the
+object to it first. For this you may pass TimeZone argument to any of the
methods which are affected by the time zone (all methods getting date
components and the date formatting ones, for example). In particular, the
Format() family of methods accepts a TimeZone parameter and this allows to
void wxDocParentFrame::OnMRUFile(wxCommandEvent& event)
{
- wxString f(m_docManager->GetHistoryFile(event.GetSelection() - wxID_FILE1));
+ wxString f(m_docManager->GetHistoryFile(event.GetId() - wxID_FILE1));
if (f != "")
(void)m_docManager->CreateDocument(f, wxDOC_SILENT);
}
the message wxEVENT\_TYPE\_TEXT\_ENTER\_COMMAND (otherwise pressing <Enter> is
either processed internally by the control or used for navigation between
dialog controls).}
-\twocolitem{\windowstyle{wxTE\_PROCESS\_TAB}}{The control will receieve
+\twocolitem{\windowstyle{wxTE\_PROCESS\_TAB}}{The control will receive
EVT\_CHAR messages for TAB pressed - normally, TAB is used for passing to the
next control in a dialog instead. For the control created with this style,
you can still use Ctrl-Enter to pass to the next control from the keyboard.}
control. In other words, it allows to limit the text value length to {\it len}
not counting the terminating {\tt NUL} character.
-If {\it len} is $0$, the previously set max length limi, if any, is discarded
+If {\it len} is $0$, the previously set max length limit, if any, is discarded
and the user may enter as much text as the underlying native text control
widget supports (typically at least 32Kb).
s should make it clear that using
encodings is less easy than it might seem. The problems arise both from the
fact that the standard encodings for the given language (say Russian, which is
-written in Cyrillic) are different on differe nt platforms and because the
+written in Cyrillic) are different on different platforms and because the
fonts in the given encoding might just not be installed (this is especially a
-problem with Unix, or, in general, not Win32, systems).
+problem with Unix, or, in general, non-Win32 systems).
To allow to see clearer in this, \helpref{wxFontEnumerator}{wxfontenumerator}
class may be used to enumerate both all available encodings and to find the
\perlnote{In wxPerl the constructor accepts as parameter an optional scalar,
and stores it as client data. You may retrieve this data by calling
- {\bf GetData()}, and set it by callling {\bf SetData( data ).}
+ {\bf GetData()}, and set it by calling {\bf SetData( data ).}
}
\membersection{wxTreeItemData::\destruct{wxTreeItemData}}
\subsection{Config sample}\label{sampleconfig}
This sample demonstrates the \helpref{wxConfig}{wxconfigbase} classes in a platform
-indenpedent way, i.e. it uses text based files to store a given configuration under
+independent way, i.e. it uses text based files to store a given configuration under
Unix and uses the Registry under Windows.
See \helpref{wxConfig overview}{wxconfigoverview} for the descriptions of all
\subsection{Dialup sample}\label{sampledialup}
This sample shows \helpref{wxDialUpManager}{wxdialupmanager}
-class. It displays in the status bar the information gathered through itsi
-nterface: in particular, the current connection status (online or offline) and
+class. It displays in the status bar the information gathered through its
+interface: in particular, the current connection status (online or offline) and
whether the connection is permanent (in which case a string `LAN' appears in
-the thrid status bar field - but note that you may have be on a LAN not
+the third status bar field - but note that you may have be on a LAN not
connected to the Internet, in which case you will not see this) or not.
Using the menu entries, you may also dial or hang up the line if you have a
higher level from using the {\tt EVT\_CHAR} macro. All characters will be logged
in a log window at the bottom of the main window. By pressing some of the function
keys, you can test some actions in the text ctrl as well as get statistics on the
-text ctrls, which is useful for testing if these stastitics actually are correct.
+text ctrls, which is useful for testing if these statistics actually are correct.
Thirdly, on platforms which support it, the sample will offer to copy text to the
\helpref{wxClipboard}{wxclipboard} and to paste text from it. The GTK version will
SetSizer( topsizer ); // actually set the sizer
topsizer->Fit( this ); // set size to minimum size as calculated by the sizer
- topsizer->SetSizeHints( this ); // set size hints to honour mininum size
+ topsizer->SetSizeHints( this ); // set size hints to honour minimum size
}
\end{verbatim}
In order to query the size of notebook page, this page needs to have its
own sizer, otherwise the wxNotebookSizer will ignore it. Notebook pages
-get their size by assigning one to them using \helpref{wxWindow::SetSizer}{wxwindowsetsizer}
+get their sizer by assigning one to them using \helpref{wxWindow::SetSizer}{wxwindowsetsizer}
and setting the auto-layout option to TRUE using
\helpref{wxWindow::SetAutoLayout}{wxwindowsetautolayout}. Here is one
example showing how to add a notebook page that the notebook sizer is
\func{wxInputStream *}{GetInputStream}{\void}
Creates a new input stream on the the specified URL. You can use all but seek
-functionnality of wxStream. Seek isn't available on all stream. For example,
+functionality of wxStream. Seek isn't available on all stream. For example,
http or ftp streams doesn't deal with it.
\wxheading{Return value}
If the printing framework is enabled in the library, this function returns a
\rtfsp\helpref{wxPrintout}{wxprintout} object for the purposes of printing. It should create a new object
-everytime it is called; the framework will delete objects it creates.
+every time it is called; the framework will delete objects it creates.
By default, this function returns an instance of wxDocPrintout, which prints
and previews one page by calling wxView::OnDraw.
\constfunc{virtual void}{ClientToScreen}{\param{int* }{x}, \param{int* }{y}}
-\perlnote{In wxPerl this method returns a 2-element list intead of
+\perlnote{In wxPerl this method returns a 2-element list instead of
modifying its parameters.}
\constfunc{virtual wxPoint}{ClientToScreen}{\param{const wxPoint\&}{ pt}}
For the x dimension, the pixels are multiplied by 4 and then divided by the average
character width.
-For the y dimension, the pixels are multipled by 8 and then divided by the average
+For the y dimension, the pixels are multiplied by 8 and then divided by the average
character height.
\wxheading{Remarks}
different window classes can be destroyed differently. Frames and dialogs
are not destroyed immediately when this function is called - they are added
to a list of windows to be deleted on idle time, when all the window's events
-have been processed. This prevents problems with events being sent to non-existant
+have been processed. This prevents problems with events being sent to non-existent
windows.
\wxheading{Return value}
\func{virtual void}{DragAcceptFiles}{\param{bool}{ accept}}
-Enables or disables elibility for drop file events (OnDropFiles).
+Enables or disables eligibility for drop file events (OnDropFiles).
\wxheading{Parameters}
\constfunc{bool}{IsExposed}{\param{wxRect }{\&rect}}
-Returns {\tt TRUE} if the given point or rectange area has been exposed since the
+Returns {\tt TRUE} if the given point or rectangle area has been exposed since the
last repaint. Call this in an paint event handler to optimize redrawing by
only redrawing those areas, which have been exposed.
%% or dialog box using the window manager (X) or system menu (Windows).
%%
%% {\bf Note:} This is an obsolete function.
-%% It is superceded by the \helpref{wxWindow::OnCloseWindow}{wxwindowonclosewindow} event
+%% It is superseded by the \helpref{wxWindow::OnCloseWindow}{wxwindowonclosewindow} event
%% handler.
%%
%% \wxheading{Return value}
and Validate() methods will recursively descend into all children of the
window if it has this style flag set.}
\twocolitem{\windowstyle{wxWS\_EX\_BLOCK\_EVENTS}}{Normally, the command
-events are propagared upwards to the window parent recursively until a handler
+events are propagated upwards to the window parent recursively until a handler
for them is found. Using this style allows to prevent them from being
propagated beyond this window. Notice that wxDialog has this style on by
default for the reasons explained in the
\twocolitem{\windowstyle{wxWS\_EX\_TRANSIENT}}{This can be used to prevent a
window from being used as an implicit parent for the dialogs which were
created without a parent. It is useful for the windows which can disappear at
-any moment as creating childs of such windows results in fatal problems.}
+any moment as creating children of such windows results in fatal problems.}
\twocolitem{\windowstyle{wxFRAME\_EX\_CONTEXTHELP}}{Under Windows, puts a query button on the
caption. When pressed, Windows will go into a context-sensitive help mode and wxWindows will send
a wxEVT\_HELP event if the user clicked on an application window.
be used at all.
Note that when using this functions under GTK, you will disable the so called "themes",
-i.e. the user chosen apperance of windows and controls, including the themes of
+i.e. the user chosen appearance of windows and controls, including the themes of
their parent windows.
\wxheading{See also}
\helpref{wxWizardPage}{wxwizardpage} implementation: it just returns the
pointers given to its constructor from GetNext() and GetPrev() functions.
-This makes it very easy to use the obejcts of this class in the wizards where
+This makes it very easy to use the objects of this class in the wizards where
the pages order is known statically - on the other hand, if this is not the
case you must derive your own class from \helpref{wxWizardPage}{wxwizardpage}
instead.
includes a collection of Python modules and an extension module
(native code). It provides a series of Python classes that mirror (or
shadow) many of the wxWindows GUI classes. This extension module
-attempts to mirror the class heirarchy of wxWindows as closely as
+attempts to mirror the class hierarchy of wxWindows as closely as
possible. This means that there is a wxFrame class in wxPython that
looks, smells, tastes and acts almost the same as the wxFrame class in
the C++ version.
-wxPython is very versitile. It can be used to create standalone GUI
+wxPython is very versatile. It can be used to create standalone GUI
applications, or in situations where Python is embedded in a C++
application as an internal scripting or macro language.
So why would you want to use wxPython over just C++ and wxWindows?
Personally I prefer using Python for everything. I only use C++ when I
-absolutely have to eek more performance out of an algorithm, and even
+absolutely have to eke more performance out of an algorithm, and even
then I usually code it as an extension module and leave the majority
of the program in Python.
\wxheading{Tkinter}
-Tkinter is the defacto standard GUI for Python. It is available
+Tkinter is the de facto standard GUI for Python. It is available
on nearly every platform that Python and Tcl/TK are. Why Tcl/Tk?
Well because Tkinter is just a wrapper around Tcl's GUI toolkit, Tk.
This has its upsides and its downsides...
\membersection{Constructors and assignment operators}
-A strign may be constructed either from a C string, (some number of copies of)
+A string may be constructed either from a C string, (some number of copies of)
a single character or a wide (UNICODE) string. For all constructors (except the
default which creates an empty string) there is also a corresponding assignment
operator.
Many functions in this section take a character index in the string. As with C
strings and/or arrays, the indices start from $0$, so the first character of a
string is string[$0$]. Attempt to access a character beyond the end of the
-string (which may be even $0$ if the string is empty) will provocate an assert
+string (which may be even $0$ if the string is empty) will provoke an assert
failure in \helpref{debug build}{debuggingoverview}, but no checks are done in
release builds.
\helpref{StartsWith}{wxstringstartswith} is helpful when parsing a line of
text which should start with some predefined prefix and is more efficient than
-doing direct string comparaison as you would also have to precalculate the
+doing direct string comparison as you would also have to precalculate the
length of the prefix then.
\helpref{Cmp}{wxstringcmp}\\
\membersection{Case conversion}
The MakeXXX() variants modify the string in place, while the other functions
-return a new string which containts the original text converted to the upper or
+return a new string which contains the original text converted to the upper or
lower case and leave the original string unchanged.
\helpref{MakeUpper}{wxstringmakeupper}\\
\membersection{Memory management}
-These are "advanced" functions and they will be needed quite rarily.
+These are "advanced" functions and they will be needed quite rarely.
\helpref{Alloc}{wxstringalloc} and \helpref{Shrink}{wxstringshrink} are only
interesting for optimization purposes.
\helpref{GetWriteBuf}{wxstringgetwritebuf} may be very useful when working with
\func{}{wxStringBuffer}{\param{const wxString\& }{str}, \param{size\_t }{len}}
Constructs a writable string buffer object associated with the given string
-and containing enough space for at least {\it len} characters. Basicly, this
+and containing enough space for at least {\it len} characters. Basically, this
is equivalent to calling \helpref{GetWriteBuf}{wxstringgetwritebuf} and
saving the result.
Creates an object (menu, dialog, control, ...) from an XML node.
Should check for validity. {\it parent} is a higher-level object (usually window, dialog or panel)
-that is often neccessary to create the resource.
+that is often necessary to create the resource.
If {\bf instance} is non-NULL it should not create a new instance via 'new' but
should rather use this one, and call its Create method.
'make install' will install wx-config script that can (and should) be used
to get compiler flags that are needed to build your program. wx-config --cxxflags
-will output neccessary C++ compiler flags and wx-config --libs will list all
+will output necessary C++ compiler flags and wx-config --libs will list all
needed libraries. See an example of wxWindows application makefile:
minimal: minimal.o
If you want to do some more serious cross-platform programming with wxWindows,
such as for GTK and Motif, you can now build two complete libraries and use
-them concurretly. For this end, you have to create a directory for each build
+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
and test them concurrently. Most typically, this would be a version configured
with --enable-debug_flag and one without. Note, that only one build can currently
You get errors during compilation: The reason is that you probably have a broken
compiler, which includes almost everything that is called gcc. If you use gcc 2.8
-you have to disable optimsation as the compiler will give up with an internal
+you have to disable optimisation as the compiler will give up with an internal
compiler error.
If there is just any way for you to use egcs, use egcs. We cannot fix gcc.
i.e. if it says "--disable-threads" it means that threads
are enabled by default.
-Many of the confiugre options have been thoroughly tested
+Many of the configure options have been thoroughly tested
in wxWindows snapshot 6, but not yet all (ODBC not).
You have to add --with-motif on platforms, where Motif is
-not the default (on Linux, configure will deafult to GTK).
+not the default (on Linux, configure will default to GTK).
--without-gtk Don't use the GIMP ToolKit (GTK)
--enable-no_deps Enable compilation without creation of
dependency information.
- --enable-permissive Enable compilation without creation of
- giving erros as soon as you compile with
- Solaris ANSI-defying headers...
+ --enable-permissive Enable compilation without checking for strict
+ ANSI conformance. Useful to prevent the build
+ dying with errors as soon as you compile with
+ Solaris' ANSI-defying headers.
--enable-mem_tracing Add built-in memory tracing.
* Feature Options
-------------------
-Many of the confiugre options have been thoroughly tested
+Many of the configure options have been thoroughly tested
in wxWindows snapshot 6, but not yet all (ODBC not).
When producing an executable that is linked statically with wxGTK
--disable-clipboard Disables Clipboard.
- --disable-serial Disables object instance serialiasation.
+ --disable-serial Disables object instance serialisation.
--disable-streams Disables the wxStream classes.
warning messages depending in your compiler.
If you want to be more selective, you can change into a specific
-directiry and type "make" there.
+directory and type "make" there.
-Then you may install the library and it's header files under
+Then you may install the library and its header files under
/usr/local/include/wx and /usr/local/lib respectively. You
have to log in as root (i.e. run "su" and enter the root
password) and type
rm -f *.o minimal
This is certain to become the standard way unless we decide
-to sitch to tmake.
+to stick to tmake.
2) The other way creates a project within the source code
directories of wxWindows. For this endeavour, you'll need
You MUST use the 'cleanall' target (with FINAL=1 or FINAL=0)
before making a different configuration, because otherwise
object files used to build the previous configuration may be
- used accidentally for the current configuation. You might see
+ used accidentally for the current configuration. You might see
this manifested in unexpected link errors or warnings. This problem
doesn't occur when using project files to build wxWindows.
32-bit compilation only (partially) supported at present, using SC++ 6.1.
Some functionality is missing using this compiler (see makefile).
Add -D__WIN95__ if your SC++ has Windows 95 support, and ignore
-Step (2). 16-bit compilation is left as an excercise for the user!
+Step (2). 16-bit compilation is left as an exercise for the user!
Salford C++ compilation
-----------------------
Add centring, right justify styles to wxStaticText.
-Extend wxLocale to get more locale settings (currence,
+Extend wxLocale to get more locale settings (currency,
date/time, decimal separator and so on)
LOW PRIORITY (MEDIUM TERM)
wxWindows programs but is required for all Windows applications).
-For your convinience, below is an example manifest. It should be put in a
+For your convenience, below is an example manifest. It should be put in a
file called "yourapp.exe.manifest" and put in the same directory where
"yourapp.exe" resides. Alternatively, you can include the manifest in your
applications resource section. Please see the MSDN documentation at
covered by the GNU Library General Public Licence, with an
exception notice for binary distribution.
-- licencdoc.txt: the wxWindows Documentation Licence.
+- licendoc.txt: the wxWindows Documentation Licence.
- lgpl.txt: the text of the GNU Library General Public Licence.
of your application, don't forget that it is linked against
GTK+ (or Lesstif) which is covered by LGPL *without* exception
notice. Under Linux systems your app is probably linked
-against LGPL glibc as well. Please read carefuly LGPL, section 6.
+against LGPL glibc as well. Please read carefully LGPL, section 6.
which describes conditions for distribution of closed source applications
-linked against LGPL library. Basically you should link dynamicaly and
+linked against LGPL library. Basically you should link dynamically and
include source code of LGPL libraries with your product (unless it is
already present in user's system - like glibc usually is).
If compiled with --enable-odbc (Unix only), wxWindows library will
( from http://www.openvms.digital.com/openvms/products/ips/gtk.html )
-Redefine the logical SYS$LIBRARY in such a way that it also points
- to the includefile/library directories of the obove packages:
+ to the includefile/library directories of the above packages:
i.e.
$ define sys$library sys$sysroot:[syslib],-
$disk2:[joukj.public.xpm.xpm.lib],-
if You encounter these, replace mms by mms/ignore=warning in the
following
- -Now build evrything using one of the following
+ -Now build everything using one of the following
mms
mms gtk
mms motif
in the main directory of the distribution. Without an argument both wxGTK
- and wxMOTIF are build. The libraies are build in the [.lib] directory.
- All the samples I tried are build automatically.
+ and wxMOTIF are built. The libraries are built in the [.lib] directory.
+ All the samples I tried are built automatically.
-I think in general wxGTK is better maintained, so that version is my
first choice.
3. Create the makefiles for Windows compilers. There are several ways to do
it:
- a) copy the makefiles from samples/minimal, replace all occurences of
+ a) copy the makefiles from samples/minimal, replace all occurrences of
minimal with foo
b) use makegen (sources are under utils/makegen)
c) use projgen
If you wish to generate documentation for wxHTML Help Viewer
(or Windows HTML Help), set htmlWorkshopFiles to true in your
tex2rtf.ini file. See also the wxHTML Notes section in the
-wxWindows manual. To futher speed-up HTML help books loading
+wxWindows manual. To further speed-up HTML help books loading
in your application, you may use hhp2cached (utils/hhp2cached).
src/msw/makefile.vc contains targets for generating various
Solution 1</h3>
<h4>
-<a href="http://biolpc22.york.ac.uk/wx/bc/download.html">Download</a> a zip file which contains modifed
+<a href="http://biolpc22.york.ac.uk/wx/bc/download.html">Download</a> a zip file which contains modified
cpp, mak and bpr files - it will overwrite your wx distribution cpp files!</h4>
<h4>
</ul>
I found in CBuilder 1 that the <tt>idetomak</tt> utility did not manage
to convert all the samples, but <tt>idetobpr</tt> worked OK in CBuilder
-3 and 4. I have a report that not all the bpr files made inb CBuilder 4
+3 and 4. I have a report that not all the bpr files made in CBuilder 4
are correct
<h2>
Error with ODBC32</h2>
-Sometimes you get an error saying that there are unreolved externals in
-ODBC. The soltuion is to run a command prompt in your <b><tt>wx\lib </tt></b>directory
+Sometimes you get an error saying that there are unresolved externals in
+ODBC. The solution is to run a command prompt in your <b><tt>wx\lib </tt></b>directory
and use the <b><tt>implib </tt></b>command:
<p><tt>C:\wx\lib><b>implib odbc32 c:\windows\system\odbc32.dll</b></tt>
<p>This creates the necessary library, odbc32.lib
=====================================
There are two IDE files. src\bc32.ide should help you to
-create the wxWindows libraries from within the Ide of Borlands
+create the wxWindows libraries from within the Ide of Borland's
C++, v. 5.x. Note that this doesn't include debugging code: you
need to change the settings if you wish to include debug
information. Previously, bc32d.ide was supplied with debug
Subject: Re: [wx-users] How to learn using wx-windows <BR>
Reply-To: wx-users@wxwindows.org<P>
-> Reading the Linux Journal article on wxpython, and having used wxclips<BR>
-> I got interested in wxwindows as a development interface. However, the<BR>
-> programming experience I got is old, and from a former generation (For-<BR>
-> tran). I'd like to refresh my experience and start in C++. Will<BR>
-
> wx-windows be a very high step to take?<P>
+> Reading the Linux Journal article on wxpython, and having used wxclips<BR>
+> I got interested in wxwindows as a development interface. However, the<BR>
+> programming experience I got is old, and from a former generation (For-<BR>
+> tran). I'd like to refresh my experience and start in C++. Will<BR>
+
> wx-windows be a very high step to take?<P>
I'm new to wxWindows myself, but I'd like to answer this question
anyway. In the past two years I've learned two similar frameworks
Besides the C++ Programming Language, by Bjarne Stroustrup, the
"official" guide to C++, I highly recommend Inside the C++ Object Model,
-by Stanley B. Lippman. (Lipmann was one of the C++ honchos at Bell
+by Stanley B. Lippman. (Lippman was one of the C++ honchos at Bell
Labs.) This book will tell you what _not_ to do, as well as why
everything in C++ is as it is. If you are confused by anything in C++,
Lippman's book is the cure.<P>
Learn as much as you can about the String class; after using a good
String class you'll never want to use C's string functions again.
-wxWindows contains other nifty utilty classes as well.<P>
+wxWindows contains other nifty util
ity classes as well.<P>
The application class, wxApp, contains the main event loop. Learn about
event handling and event tables (reading sample code will help). Almost
into the executable.<P>
You can decide to use only XPMs on Windows and Unix, or you could use XPMs on Unix and
-Windows icons under Windows -- the latter will require some #idefs in your code or use of the wxICON macro.<P>
+Windows icons under Windows -- the latter will require some #i
fdefs in your code or use of the wxICON macro.<P>
If you are using a compiler such as Borland C++, Visual C++ or Watcom C++, you
can use the provided icon editor. However, if using Cygwin or Mingw32, there
<PRE>
c:\wx2\include,c:\wx2\contrib\include
</PRE>
-<P>(and of couse any other directories you wish to use in your project).<P>
+<P>(and of cou
rse any other directories you wish to use in your project).<P>
<DT><B>C/C++: Precompiled Headers</B><DD>
<PRE>
../../include/base,../../include/msw
</PRE>
-<P>(and of couse any other directories you wish to use in your project).<P>
+<P>(and of cou
rse any other directories you wish to use in your project).<P>
<DT><B>C/C++: Precompiled Headers</B><DD>
To manage this sanely we need a sufficiently descriptive and logical
labelling convention for file and install path names -- this document (at
-least at it's time of writing) describes the system we have adopted.
+least at its time of writing) describes the system we have adopted.
It is not fine grained enough to include every possible build configuration
for wxWindows, but is encompassing enough to maintain a relatively complete
appropriate toolkit in addition to wxUniversal - in fact, you should download
them first and then unpack wxUniversal in the same directory.
- The requirments for wxUniversal are the same as for the underlying low level
+ The requirements for wxUniversal are the same as for the underlying low level
toolkit.
2. Installing under Win32
22th June '99: wxWINE 2.1 snapshot 7 released
-The numbering is just in synch with the wxGTK numbering as this
+The numbering is just in sync with the wxGTK numbering as this
is actually the first ever release of wxWINE.
This snapshot just demonstrates that the complete build environment
----------------
Most C++ compilers cannot compile the WINE sources yet (this includes
-all versions of g++ and ecgs) so you have to make a minimal change
+all versions of g++ and egcs) so you have to make a minimal change
and recompile all of WINE in order to get anywhere.
This change has do be applied to the /include/windef.h file, line 59
-in the section "Calling convention defintions", where the sources
+in the section "Calling convention definitions", where the sources
reads:
#if __i386__
> exit
On all variants of Unix except Linux (and maybe except *BSD), shared libraries
-are not supportet out of the box due to the utter stupidity of libtool, so you'll
+are not supported out of the box due to the utter stupidity of libtool, so you'll
have to do this to get shared library support:
> ./configure --with-wine --disable-static --enable-shared
If you want to do some more serious cross-platform programming with wxWindows,
such as for GTK and Motif, you can now build two complete libraries and use
-them concurretly. For this end, you have to create a directory for each build
+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
and test them concurrently. Most typically, this would be a version configured
with --enable-debug_flag and one without. Note, that only one build can currently
You get errors during compilation: The reason is that you probably have a broken
compiler, which includes almost everything that is called gcc. If you use gcc 2.8
-you have to disable optimsation as the compiler will give up with an internal
+you have to disable optimisation as the compiler will give up with an internal
compiler error.
If there is just any way for you to use egcs, use egcs. We cannot fix gcc.
i.e. if it says "--disable-threads" it means that threads
are enabled by default.
-Many of the confiugre options have been thoroughly tested
+Many of the configure options have been thoroughly tested
in wxWindows snapshot 6, but not yet all (ODBC not).
You must do this by running configure with either of:
* Feature Options
-------------------
-Many of the confiugre options have been thoroughly tested
+Many of the configure options have been thoroughly tested
in wxWindows snapshot 6, but not yet all (ODBC not).
When producing an executable that is linked statically with wxGTK
--disable-clipboard Disables Clipboard.
- --disable-serial Disables object instance serialiasation.
+ --disable-serial Disables object instance serialisation.
--disable-streams Disables the wxStream classes.
warning messages depending in your compiler.
If you want to be more selective, you can change into a specific
-directiry and type "make" there.
+directory and type "make" there.
-Then you may install the library and it's header files under
+Then you may install the library and its header files under
/usr/local/include/wx and /usr/local/lib respectively. You
have to log in as root (i.e. run "su" and enter the root
password) and type
rm -f *.o minimal
This is certain to become the standard way unless we decide
-to sitch to tmake.
+to stick to tmake.
2) The other way creates a project within the source code
directories of wxWindows. For this endeavour, you'll need
If you want to do some more serious cross-platform programming with wxWindows,
such as for GTK and X11, you can now build two complete libraries and use
-them concurretly. For this end, you have to create a directory for each build
+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
and test them concurrently. Most typically, this would be a version configured
with --enable-debug_flag and one without. Note, that only one build can currently
You get errors during compilation: The reason is that you probably have a broken
compiler, which includes almost everything that is called gcc. If you use gcc 2.8
-you have to disable optimsation as the compiler will give up with an internal
+you have to disable optimisation as the compiler will give up with an internal
compiler error.
If there is just any way for you to use egcs, use egcs. We cannot fix gcc.
i.e. if it says "--disable-threads" it means that threads
are enabled by default.
-Many of the confiugre options have been thoroughly tested
+Many of the configure options have been thoroughly tested
in wxWindows snapshot 6, but not yet all (ODBC not).
You have to add --with-x11 on platforms, where X11 is
-not the default (on Linux, configure will deafult to GTK).
+not the default (on Linux, configure will default to GTK).
--without-gtk Don't use the GIMP ToolKit (GTK).
--enable-no_deps Enable compilation without creation of
dependency information.
- --enable-permissive Enable compilation without creation of
- giving erros as soon as you compile with
- Solaris ANSI-defying headers...
+ --enable-permissive Enable compilation without checking for strict
+ ANSI conformance. Useful to prevent the build
+ dying with errors as soon as you compile with
+ Solaris' ANSI-defying headers.
--enable-mem_tracing Add built-in memory tracing.
* Feature Options
-------------------
-Many of the confiugre options have been thoroughly tested
+Many of the configure options have been thoroughly tested
in wxWindows snapshot 6, but not yet all (ODBC not).
When producing an executable that is linked statically with wxGTK
--disable-clipboard Disables Clipboard.
- --disable-serial Disables object instance serialiasation.
+ --disable-serial Disables object instance serialisation.
--disable-streams Disables the wxStream classes.
warning messages depending in your compiler.
If you want to be more selective, you can change into a specific
-directiry and type "make" there.
+directory and type "make" there.
-Then you may install the library and it's header files under
+Then you may install the library and its header files under
/usr/local/include/wx and /usr/local/lib respectively. You
have to log in as root (i.e. run "su" and enter the root
password) and type
rm -f *.o minimal
This is certain to become the standard way unless we decide
-to sitch to tmake.
+to stick to tmake.
2) The other way creates a project within the source code
directories of wxWindows. For this endeavour, you'll need
projects / wxWidgets.git / commitdiff
