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

Spelling fixes from Andreas Mohr (patch #1360064)

Browse Source 
git-svn-id: https://svn.wxwidgets.org/svn/wx/wxWidgets/trunk@36199 c3d73ce0-8a6f-49c7-b76d-6d57e0e08775
This commit is contained in:
Mart Raudsepp
2005-11-19 01:07:56 +00:00
parent 8b28584104
commit 90e572f1e5
33 changed files with 113 additions and 113 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@@ -1630,12 +1630,12 @@ Beginning support for handling international formatting specifically on dates
and floats.
\begin{verbatim}
wxString s_Field; // Formated String for Output
wxString s_Format[7]; // Formated Objects - TIMESTAMP has
wxString s_Field; // Formatted String for Output
wxString s_Format[7]; // Formatted Objects - TIMESTAMP has
the biggest (7)
wxString s_Amount[7]; // Formated Objects - amount of
wxString s_Amount[7]; // Formatted Objects - amount of
things that can be formatted
int i_Amount[7]; // Formated Objects -
int i_Amount[7]; // Formatted Objects -
TT MM YYYY HH MM SS m
int i_Nation; // 0 = timestamp
1 = EU

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

@@ -501,7 +501,7 @@ This function may be used to find all selected items in the control like this:
\twocolitem{wxLIST\_NEXT\_RIGHT}{Searches for an item to the right of the specified item.}
\end{twocollist}
{\bf NB:} this parameters is only supported by wxMSW currently and ignored on
{\bf NB:} this parameter is only supported by wxMSW currently and ignored on
other platforms.
{\it state} can be a bitlist of the following:

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

@@ -13,8 +13,8 @@ recursive by default. The reason for this is that recursive mutexes are not
supported by all Unix flavours and, worse, they cannot be used with
\helpref{wxCondition}{wxcondition}.
For example, when several thread use the data stored in the linked list,
modifications to the list should be only allowed to one thread at a time
For example, when several threads use the data stored in the linked list,
modifications to the list should only be allowed to one thread at a time
because during a new node addition the list integrity is temporarily broken
(this is also called {\it program invariant}).

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

@@ -3,7 +3,7 @@
This is a small helper class to be used with \helpref{wxMutex}{wxmutex}
objects. A wxMutexLocker acquires a mutex lock in the constructor and releases
(or unlocks) the mutex in the destructor making it much more difficult to
forget to release a mutex (which, in general, will promptly lead to the serious
forget to release a mutex (which, in general, will promptly lead to serious
problems). See \helpref{wxMutex}{wxmutex} for an example of wxMutexLocker
usage.

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

@@ -20,8 +20,8 @@ decrements the counter. As soon as it reaches $0$, any subsequent calls to
counter becomes strictly positive again as the result of calling
\helpref{Post}{wxsemaphorepost} which increments the counter.
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
In general, semaphores are useful to restrict access to a shared resource
which can only be accessed by some fixed number of clients at the same time. 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
is reserved, the semaphore should be acquired by calling
@@ -43,7 +43,7 @@ No base class
\func{}{wxSemaphore}{\param{int }{initialcount = 0}, \param{int }{maxcount = 0}}
Specifying a {\it maxcount} of $0$ actually makes wxSemaphore behave as if
there is no upper limit. If maxcount is $1$ the semaphore behaves exactly as a
there is no upper limit. If maxcount is $1$, the semaphore behaves exactly as a
mutex.
{\it initialcount} is the initial value of the semaphore which must be between