]> git.saurik.com Git - wxWidgets.git/blame - docs/latex/wx/conditn.tex
changed the catalogs lookup back to the old behaviour of searching LC_MESSAGES subdir...
[wxWidgets.git] / docs / latex / wx / conditn.tex
CommitLineData
eaaa6a06
JS
1\section{\class{wxCondition}}\label{wxcondition}
2
9063ea8e
VZ
3wxCondition variables correspond to pthread conditions or to Win32 event
4objects. They may be used in a multithreaded application to wait until the
5given condition becomes true which happens when the condition becomes signaled.
6
7For example, if a worker thread is doing some long task and another thread has
f6bcfd97 8to wait until it is finished, the latter thread will wait on the condition
9063ea8e
VZ
9object and the worker thread will signal it on exit (this example is not
10perfect because in this particular case it would be much better to just
11\helpref{Wait()}{wxthreadwait} for the worker thread, but if there are several
12worker threads it already makes much more sense).
eaaa6a06 13
60ce696e 14Note that a call to \helpref{Signal()}{wxconditionsignal} may happen before the
be809868 15other thread calls \helpref{Wait()}{wxconditionwait} and, just as with the
fc4fe308
VZ
16pthread conditions, the signal is then lost and so if you want to be sure that
17you don't miss it you must keep the mutex associated with the condition
18initially locked and lock it again before calling
19\helpref{Signal()}{wxconditionsignal}. Of course, this means that this call is
20going to block until \helpref{Wait()}{wxconditionwait} is called by another
21thread.
60ce696e
VZ
22
23\wxheading{Example}
24
be809868
VZ
25This example shows how a main thread may launch a worker thread which starts
26running and then waits until the main thread signals it to continue:
60ce696e
VZ
27
28\begin{verbatim}
d30ff492 29class MySignallingThread : public wxThread
60ce696e
VZ
30{
31public:
d30ff492 32 MySignallingThread(wxMutex *mutex, wxCondition *condition)
60ce696e 33 {
be809868 34 m_mutex = mutex;
60ce696e
VZ
35 m_condition = condition;
36
37 Create();
38 }
39
40 virtual ExitCode Entry()
41 {
60ce696e
VZ
42 ... do our job ...
43
d30ff492
VZ
44 // tell the other(s) thread(s) that we're about to terminate: we must
45 // lock the mutex first or we might signal the condition before the
46 // waiting threads start waiting on it!
47 wxMutexLocker lock(m_mutex);
48 m_condition.Broadcast(); // same as Signal() here -- one waiter only
49
60ce696e
VZ
50 return 0;
51 }
52
53private:
54 wxCondition *m_condition;
d30ff492 55 wxMutex *m_mutex;
60ce696e
VZ
56};
57
58int main()
59{
be809868 60 wxMutex mutex;
c112e100 61 wxCondition condition(mutex);
be809868 62
d30ff492
VZ
63 // the mutex should be initially locked
64 mutex.Lock();
60ce696e 65
d30ff492
VZ
66 // create and run the thread but notice that it won't be able to
67 // exit (and signal its exit) before we unlock the mutex below
68 MySignallingThread *thread = new MySignallingThread(&mutex, &condition);
60ce696e 69
d30ff492 70 thread->Run();
be809868 71
d30ff492
VZ
72 // wait for the thread termination: Wait() atomically unlocks the mutex
73 // which allows the thread to continue and starts waiting
74 condition.Wait();
60ce696e 75
d30ff492 76 // now we can exit
60ce696e
VZ
77 return 0;
78}
79\end{verbatim}
f6bcfd97 80
d30ff492
VZ
81Of course, here it would be much better to simply use a joinable thread and
82call \helpref{wxThread::Wait}{wxthreadwait} on it, but this example does
83illustrate the importance of properly locking the mutex when using
84wxCondition.
85
23efb556
VZ
86\wxheading{Constants}
87
88The following return codes are returned by wxCondition member functions:
89
90\begin{verbatim}
91enum wxCondError
92{
93 wxCOND_NO_ERROR = 0, // successful completion
94 wxCOND_INVALID, // object hasn't been initialized successfully
95 wxCOND_TIMEOUT, // WaitTimeout() has timed out
96 wxCOND_MISC_ERROR // some other error
97};
98\end{verbatim}
99
eaaa6a06
JS
100\wxheading{Derived from}
101
102None.
103
954b8ae6
JS
104\wxheading{Include files}
105
106<wx/thread.h>
107
eaaa6a06
JS
108\wxheading{See also}
109
110\helpref{wxThread}{wxthread}, \helpref{wxMutex}{wxmutex}
111
112\latexignore{\rtfignore{\wxheading{Members}}}
113
f510b7b2 114\membersection{wxCondition::wxCondition}\label{wxconditionctor}
eaaa6a06 115
c112e100 116\func{}{wxCondition}{\param{wxMutex\& }{mutex}}
eaaa6a06 117
c112e100
VZ
118Default and only constructor. The {\it mutex} must be locked by the caller
119before calling \helpref{Wait}{wxconditionwait} function.
eaaa6a06 120
23efb556 121Use \helpref{IsOk}{wxconditionisok} to check if the object was successfully
dbd94b75 122initialized.
23efb556 123
f510b7b2 124\membersection{wxCondition::\destruct{wxCondition}}\label{wxconditiondtor}
eaaa6a06
JS
125
126\func{}{\destruct{wxCondition}}{\void}
127
be809868
VZ
128Destroys the wxCondition object. The destructor is not virtual so this class
129should not be used polymorphically.
eaaa6a06
JS
130
131\membersection{wxCondition::Broadcast}\label{wxconditionbroadcast}
132
133\func{void}{Broadcast}{\void}
134
be809868
VZ
135Broadcasts to all waiting threads, waking all of them up. Note that this method
136may be called whether the mutex associated with this condition is locked or
137not.
138
139\wxheading{See also}
140
141\helpref{wxCondition::Signal}{wxconditionsignal}
eaaa6a06 142
23efb556
VZ
143\membersection{wxCondition::IsOk}\label{wxconditionisok}
144
145\constfunc{bool}{IsOk}{\void}
146
147Returns {\tt true} if the object had been initialized successfully, {\tt false}
43e8916f 148if an error occurred.
23efb556 149
eaaa6a06
JS
150\membersection{wxCondition::Signal}\label{wxconditionsignal}
151
152\func{void}{Signal}{\void}
153
be809868
VZ
154Signals the object waking up at most one thread. If several threads are waiting
155on the same condition, the exact thread which is woken up is undefined. If no
156threads are waiting, the signal is lost and the condition would have to be
157signalled again to wake up any thread which may start waiting on it later.
158
159Note that this method may be called whether the mutex associated with this
160condition is locked or not.
161
162\wxheading{See also}
163
164\helpref{wxCondition::Broadcast}{wxconditionbroadcast}
eaaa6a06
JS
165
166\membersection{wxCondition::Wait}\label{wxconditionwait}
167
23efb556 168\func{wxCondError}{Wait}{\void}
eaaa6a06 169
be809868 170Waits until the condition is signalled.
eaaa6a06 171
23efb556
VZ
172This method atomically releases the lock on the mutex associated with this
173condition (this is why it must be locked prior to calling Wait) and puts the
174thread to sleep until \helpref{Signal}{wxconditionsignal} or
ddca12cf
VZ
175\helpref{Broadcast}{wxconditionbroadcast} is called. It then locks the mutex
176again and returns.
23efb556
VZ
177
178Note that even if \helpref{Signal}{wxconditionsignal} had been called before
179Wait without waking up any thread, the thread would still wait for another one
180and so it is important to ensure that the condition will be signalled after
181Wait or the thread may sleep forever.
182
183\wxheading{Return value}
184
43e8916f 185Returns {\tt wxCOND\_NO\_ERROR} on success, another value if an error occurred.
23efb556
VZ
186
187\wxheading{See also}
188
189\helpref{WaitTimeout}{wxconditionwaittimeout}
190
191
192\membersection{wxCondition::WaitTimeout}\label{wxconditionwaittimeout}
193
0f353563 194\func{wxCondError}{WaitTimeout}{\param{unsigned long}{ milliseconds}}
eaaa6a06 195
be809868
VZ
196Waits until the condition is signalled or the timeout has elapsed.
197
23efb556
VZ
198This method is identical to \helpref{Wait}{wxconditionwait} except that it
199returns, with the return code of {\tt wxCOND\_TIMEOUT} as soon as the given
200timeout expires.
eaaa6a06
JS
201
202\wxheading{Parameters}
203
23efb556 204\docparam{milliseconds}{Timeout in milliseconds}
eaaa6a06
JS
205
206\wxheading{Return value}
207
23efb556 208Returns {\tt wxCOND\_NO\_ERROR} if the condition was signalled,
dbd94b75 209{\tt wxCOND\_TIMEOUT} if the timeout elapsed before this happened or another
23efb556 210error code from wxCondError enum.
eaaa6a06 211