1998-06-14 08:11:50 -04:00
|
|
|
\section{\class{wxThread}}\label{wxthread}
|
|
|
|
|
2001-04-02 10:02:46 -04:00
|
|
|
A thread is basically a path of execution through a program. Threads are
|
1999-02-06 08:32:46 -05:00
|
|
|
sometimes called {\it light-weight processes}, but the fundamental difference
|
1999-01-02 18:02:30 -05:00
|
|
|
between threads and processes is that memory spaces of different processes are
|
|
|
|
separated while all threads share the same address space. While it makes it
|
|
|
|
much easier to share common data between several threads, it also makes much
|
1999-02-06 08:32:46 -05:00
|
|
|
easier to shoot oneself in the foot, so careful use of synchronization objects
|
1999-01-17 17:49:07 -05:00
|
|
|
such as \helpref{mutexes}{wxmutex} and/or \helpref{critical sections}{wxcriticalsection} is recommended.
|
1998-06-14 08:11:50 -04:00
|
|
|
|
1999-11-29 18:05:23 -05:00
|
|
|
There are two types of threads in wxWindows: {\it detached} and {\it joinable}
|
2001-04-02 10:02:46 -04:00
|
|
|
ones, just as in the POSIX thread API (but unlike Win32 threads where all threads
|
|
|
|
are joinable). The difference between the two is that only joinable threads
|
2003-06-14 12:55:35 -04:00
|
|
|
can return a return code -- this is returned by the Wait() function. Detached
|
2001-04-02 10:02:46 -04:00
|
|
|
threads (the default type) cannot be waited for.
|
1999-11-29 18:05:23 -05:00
|
|
|
|
|
|
|
You shouldn't hurry to create all the threads joinable, however, because this
|
2001-04-02 10:02:46 -04:00
|
|
|
has a disadvantage as well: you {\bf must} Wait() for a joinable thread or the
|
|
|
|
system resources used by it will never be freed, and you also must delete the
|
|
|
|
corresponding wxThread object yourself. In contrast, detached threads are of the
|
1999-11-29 18:05:23 -05:00
|
|
|
"fire-and-forget" kind: you only have to start a detached thread and it will
|
|
|
|
terminate and destroy itself.
|
|
|
|
|
|
|
|
This means, of course, that all detached threads {\bf must} be created on the
|
2001-04-02 10:02:46 -04:00
|
|
|
heap because the thread will call {\tt delete this;} upon termination. Joinable
|
2001-05-24 17:35:34 -04:00
|
|
|
threads may be created on the stack although more usually they will be created
|
|
|
|
on the heap as well. Don't create global thread objects because they allocate
|
|
|
|
memory in their constructor, which will cause problems for the memory checking
|
|
|
|
system.
|
1999-11-29 18:05:23 -05:00
|
|
|
|
1998-06-14 08:11:50 -04:00
|
|
|
\wxheading{Derived from}
|
|
|
|
|
|
|
|
None.
|
|
|
|
|
1999-02-15 15:41:29 -05:00
|
|
|
\wxheading{Include files}
|
|
|
|
|
|
|
|
<wx/thread.h>
|
|
|
|
|
1998-06-14 08:11:50 -04:00
|
|
|
\wxheading{See also}
|
|
|
|
|
1999-01-25 13:33:08 -05:00
|
|
|
\helpref{wxMutex}{wxmutex}, \helpref{wxCondition}{wxcondition}, \helpref{wxCriticalSection}{wxcriticalsection}
|
1998-06-14 08:11:50 -04:00
|
|
|
|
|
|
|
\latexignore{\rtfignore{\wxheading{Members}}}
|
|
|
|
|
1999-01-17 17:49:07 -05:00
|
|
|
\membersection{wxThread::wxThread}\label{wxthreadctor}
|
1998-06-14 08:11:50 -04:00
|
|
|
|
2000-07-15 15:51:35 -04:00
|
|
|
\func{}{wxThread}{\param{wxThreadKind }{kind = wxTHREAD\_DETACHED}}
|
1998-06-14 08:11:50 -04:00
|
|
|
|
2001-04-02 10:02:46 -04:00
|
|
|
This constructor creates a new detached (default) or joinable C++ thread object. It
|
2003-06-14 12:55:35 -04:00
|
|
|
does not create or start execution of the real thread -- for this you should
|
2001-04-02 10:02:46 -04:00
|
|
|
use the \helpref{Create}{wxthreadcreate} and \helpref{Run}{wxthreadrun} methods.
|
1998-06-14 08:11:50 -04:00
|
|
|
|
2000-07-15 15:51:35 -04:00
|
|
|
The possible values for {\it kind} parameters are:
|
2001-04-02 10:02:46 -04:00
|
|
|
|
2000-07-15 15:51:35 -04:00
|
|
|
\twocolwidtha{7cm}
|
|
|
|
\begin{twocollist}\itemsep=0pt
|
|
|
|
\twocolitem{{\bf wxTHREAD\_DETACHED}}{Create a detached thread.}
|
|
|
|
\twocolitem{{\bf wxTHREAD\_JOINABLE}}{Create a joinable thread}
|
|
|
|
\end{twocollist}
|
|
|
|
|
1998-06-14 08:11:50 -04:00
|
|
|
\membersection{wxThread::\destruct{wxThread}}
|
|
|
|
|
|
|
|
\func{}{\destruct{wxThread}}{\void}
|
|
|
|
|
2001-04-02 10:02:46 -04:00
|
|
|
The destructor frees the resources associated with the thread. Notice that you
|
2003-06-14 12:55:35 -04:00
|
|
|
should never delete a detached thread -- you may only call
|
1999-11-27 18:15:07 -05:00
|
|
|
\helpref{Delete}{wxthreaddelete} on it or wait until it terminates (and auto
|
|
|
|
destructs) itself. Because the detached threads delete themselves, they can
|
|
|
|
only be allocated on the heap.
|
|
|
|
|
2001-04-02 10:02:46 -04:00
|
|
|
Joinable threads should be deleted explicitly. The \helpref{Delete}{wxthreaddelete} and \helpref{Kill}{wxthreadkill} functions
|
1999-11-27 18:15:07 -05:00
|
|
|
will not delete the C++ thread object. It is also safe to allocate them on
|
|
|
|
stack.
|
1998-06-14 08:11:50 -04:00
|
|
|
|
|
|
|
\membersection{wxThread::Create}\label{wxthreadcreate}
|
|
|
|
|
2002-01-03 00:53:39 -05:00
|
|
|
\func{wxThreadError}{Create}{\param{unsigned int }{stackSize = 0}}
|
1998-06-14 08:11:50 -04:00
|
|
|
|
2001-04-02 10:02:46 -04:00
|
|
|
Creates a new thread. The thread object is created in the suspended state, and you
|
2002-01-03 00:53:39 -05:00
|
|
|
should call \helpref{Run}{wxthreadrun} to start running it. You may optionally
|
|
|
|
specify the stack size to be allocated to it (Ignored on platforms that don't
|
|
|
|
support setting it explicitly, eg. Unix).
|
1998-06-14 08:11:50 -04:00
|
|
|
|
|
|
|
\wxheading{Return value}
|
|
|
|
|
|
|
|
One of:
|
|
|
|
|
|
|
|
\twocolwidtha{7cm}
|
|
|
|
\begin{twocollist}\itemsep=0pt
|
1999-01-02 18:02:30 -05:00
|
|
|
\twocolitem{{\bf wxTHREAD\_NO\_ERROR}}{There was no error.}
|
|
|
|
\twocolitem{{\bf wxTHREAD\_NO\_RESOURCE}}{There were insufficient resources to create a new thread.}
|
|
|
|
\twocolitem{{\bf wxTHREAD\_RUNNING}}{The thread is already running.}
|
1998-06-14 08:11:50 -04:00
|
|
|
\end{twocollist}
|
|
|
|
|
1999-01-17 17:49:07 -05:00
|
|
|
\membersection{wxThread::Delete}\label{wxthreaddelete}
|
1998-06-14 08:11:50 -04:00
|
|
|
|
1999-05-19 09:46:17 -04:00
|
|
|
\func{void}{Delete}{\void}
|
1998-06-14 08:11:50 -04:00
|
|
|
|
1999-11-27 18:15:07 -05:00
|
|
|
Calling \helpref{Delete}{wxthreaddelete} is a graceful way to terminate the
|
|
|
|
thread. It asks the thread to terminate and, if the thread code is well
|
2002-01-16 01:28:11 -05:00
|
|
|
written, the thread will terminate after the next call to
|
2001-04-02 10:02:46 -04:00
|
|
|
\helpref{TestDestroy}{wxthreadtestdestroy} which should happen quite soon.
|
1999-11-27 18:15:07 -05:00
|
|
|
|
2002-01-16 01:28:11 -05:00
|
|
|
However, if the thread doesn't call \helpref{TestDestroy}{wxthreadtestdestroy}
|
1999-11-27 18:15:07 -05:00
|
|
|
often enough (or at all), the function will not return immediately, but wait
|
2001-04-02 10:02:46 -04:00
|
|
|
until the thread terminates. As it may take a long time, and the message processing
|
|
|
|
is not stopped during this function execution, message handlers may be
|
1999-11-27 18:15:07 -05:00
|
|
|
called from inside it!
|
|
|
|
|
2003-06-14 12:55:35 -04:00
|
|
|
Delete() may be called for a thread in any state: running, paused or even not
|
|
|
|
yet created. Moreover, it must be called if \helpref{Create}{wxthreadcreate} or
|
|
|
|
\helpref{Run}{wxthreadrun} fail in order to free the memory occupied by the
|
|
|
|
thread object. However, you should not call Delete() on a detached thread which
|
|
|
|
already terminated -- doing so will probably result in a crash because the
|
|
|
|
thread object doesn't exist any more.
|
1999-11-29 18:05:23 -05:00
|
|
|
|
1999-11-27 18:15:07 -05:00
|
|
|
For detached threads Delete() will also delete the C++ thread object, but it
|
|
|
|
will not do this for joinable ones.
|
1998-06-14 08:11:50 -04:00
|
|
|
|
1999-11-27 18:15:07 -05:00
|
|
|
This function can only be called from another thread context.
|
1998-06-14 08:11:50 -04:00
|
|
|
|
1999-05-19 09:46:17 -04:00
|
|
|
\membersection{wxThread::Entry}\label{wxthreadentry}
|
|
|
|
|
1999-11-27 18:15:07 -05:00
|
|
|
\func{virtual ExitCode}{Entry}{\void}
|
1999-05-19 09:46:17 -04:00
|
|
|
|
|
|
|
This is the entry point of the thread. This function is pure virtual and must
|
|
|
|
be implemented by any derived class. The thread execution will start here.
|
|
|
|
|
2001-04-02 10:02:46 -04:00
|
|
|
The returned value is the thread exit code which is only useful for
|
1999-11-27 18:15:07 -05:00
|
|
|
joinable threads and is the value returned by \helpref{Wait}{wxthreadwait}.
|
1999-05-19 09:46:17 -04:00
|
|
|
|
1999-11-27 18:15:07 -05:00
|
|
|
This function is called by wxWindows itself and should never be called
|
|
|
|
directly.
|
1998-06-14 08:11:50 -04:00
|
|
|
|
2000-03-19 08:10:02 -05:00
|
|
|
\membersection{wxThread::Exit}\label{wxthreadexit}
|
|
|
|
|
|
|
|
\func{void}{Exit}{\param{ExitCode }{exitcode = 0}}
|
|
|
|
|
2001-04-02 10:02:46 -04:00
|
|
|
This is a protected function of the wxThread class and thus can only be called
|
|
|
|
from a derived class. It also can only be called in the context of this
|
2000-03-19 08:10:02 -05:00
|
|
|
thread, i.e. a thread can only exit from itself, not from another thread.
|
|
|
|
|
|
|
|
This function will terminate the OS thread (i.e. stop the associated path of
|
2002-01-16 01:28:11 -05:00
|
|
|
execution) and also delete the associated C++ object for detached threads.
|
2000-03-19 08:10:02 -05:00
|
|
|
\helpref{wxThread::OnExit}{wxthreadonexit} will be called just before exiting.
|
|
|
|
|
1999-12-06 07:31:04 -05:00
|
|
|
\membersection{wxThread::GetCPUCount}\label{wxthreadgetcpucount}
|
|
|
|
|
|
|
|
\func{static int}{GetCPUCount}{\void}
|
|
|
|
|
|
|
|
Returns the number of system CPUs or -1 if the value is unknown.
|
|
|
|
|
|
|
|
\wxheading{See also}
|
|
|
|
|
|
|
|
\helpref{SetConcurrency}{wxthreadsetconcurrency}
|
|
|
|
|
2002-01-16 01:28:11 -05:00
|
|
|
\membersection{wxThread::GetCurrentId}\label{wxthreadgetcurrentid}
|
|
|
|
|
|
|
|
\func{static unsigned long}{GetCurrentId}{\void}
|
|
|
|
|
|
|
|
Returns the platform specific thread ID of the current thread as a
|
|
|
|
long. This can be used to uniquely identify threads, even if they are
|
|
|
|
not wxThreads.
|
|
|
|
|
1999-11-27 18:15:07 -05:00
|
|
|
\membersection{wxThread::GetId}\label{wxthreadgetid}
|
|
|
|
|
|
|
|
\constfunc{unsigned long}{GetId}{\void}
|
1998-06-14 08:11:50 -04:00
|
|
|
|
2001-04-02 10:02:46 -04:00
|
|
|
Gets the thread identifier: this is a platform dependent number that uniquely identifies the
|
1999-01-17 17:49:07 -05:00
|
|
|
thread throughout the system during its existence (i.e. the thread identifiers may be reused).
|
1998-06-14 08:11:50 -04:00
|
|
|
|
|
|
|
\membersection{wxThread::GetPriority}\label{wxthreadgetpriority}
|
|
|
|
|
|
|
|
\constfunc{int}{GetPriority}{\void}
|
|
|
|
|
|
|
|
Gets the priority of the thread, between zero and 100.
|
|
|
|
|
1999-11-27 18:15:07 -05:00
|
|
|
The following priorities are defined:
|
1998-06-14 08:11:50 -04:00
|
|
|
|
|
|
|
\twocolwidtha{7cm}
|
|
|
|
\begin{twocollist}\itemsep=0pt
|
1998-07-17 08:34:50 -04:00
|
|
|
\twocolitem{{\bf WXTHREAD\_MIN\_PRIORITY}}{0}
|
|
|
|
\twocolitem{{\bf WXTHREAD\_DEFAULT\_PRIORITY}}{50}
|
|
|
|
\twocolitem{{\bf WXTHREAD\_MAX\_PRIORITY}}{100}
|
1998-06-14 08:11:50 -04:00
|
|
|
\end{twocollist}
|
|
|
|
|
|
|
|
\membersection{wxThread::IsAlive}\label{wxthreadisalive}
|
|
|
|
|
|
|
|
\constfunc{bool}{IsAlive}{\void}
|
|
|
|
|
2003-01-17 19:16:34 -05:00
|
|
|
Returns true if the thread is alive (i.e. started and not terminating).
|
1998-06-14 08:11:50 -04:00
|
|
|
|
1999-11-27 18:15:07 -05:00
|
|
|
\membersection{wxThread::IsDetached}\label{wxthreadisdetached}
|
|
|
|
|
|
|
|
\constfunc{bool}{IsDetached}{\void}
|
|
|
|
|
2003-01-17 19:16:34 -05:00
|
|
|
Returns true if the thread is of the detached kind, false if it is a joinable one.
|
1999-11-27 18:15:07 -05:00
|
|
|
|
1998-06-14 08:11:50 -04:00
|
|
|
\membersection{wxThread::IsMain}\label{wxthreadismain}
|
|
|
|
|
1999-11-27 18:15:07 -05:00
|
|
|
\func{static bool}{IsMain}{\void}
|
1998-06-14 08:11:50 -04:00
|
|
|
|
2003-01-17 19:16:34 -05:00
|
|
|
Returns true if the calling thread is the main application thread.
|
1998-06-14 08:11:50 -04:00
|
|
|
|
1999-01-17 17:49:07 -05:00
|
|
|
\membersection{wxThread::IsPaused}\label{wxthreadispaused}
|
|
|
|
|
|
|
|
\constfunc{bool}{IsPaused}{\void}
|
|
|
|
|
2003-01-17 19:16:34 -05:00
|
|
|
Returns true if the thread is paused.
|
1999-01-17 17:49:07 -05:00
|
|
|
|
|
|
|
\membersection{wxThread::IsRunning}\label{wxthreadisrunning}
|
1998-06-14 08:11:50 -04:00
|
|
|
|
1999-01-17 17:49:07 -05:00
|
|
|
\constfunc{bool}{IsRunning}{\void}
|
1998-06-14 08:11:50 -04:00
|
|
|
|
2003-01-17 19:16:34 -05:00
|
|
|
Returns true if the thread is running.
|
1999-01-17 17:49:07 -05:00
|
|
|
|
|
|
|
\membersection{wxThread::Kill}\label{wxthreadkill}
|
|
|
|
|
|
|
|
\func{wxThreadError}{Kill}{\void}
|
|
|
|
|
|
|
|
Immediately terminates the target thread. {\bf This function is dangerous and should
|
|
|
|
be used with extreme care (and not used at all whenever possible)!} The resources
|
|
|
|
allocated to the thread will not be freed and the state of the C runtime library
|
|
|
|
may become inconsistent. Use \helpref{Delete()}{wxthreaddelete} instead.
|
1998-06-14 08:11:50 -04:00
|
|
|
|
2001-04-02 10:02:46 -04:00
|
|
|
For detached threads Kill() will also delete the associated C++ object.
|
|
|
|
However this will not happen for joinable threads and this means that you will
|
2000-03-20 12:39:18 -05:00
|
|
|
still have to delete the wxThread object yourself to avoid memory leaks.
|
|
|
|
In neither case \helpref{OnExit}{wxthreadonexit} of the dying thread will be
|
|
|
|
called, so no thread-specific cleanup will be performed.
|
1999-11-27 18:15:07 -05:00
|
|
|
|
2000-03-19 08:10:02 -05:00
|
|
|
This function can only be called from another thread context, i.e. a thread
|
2001-04-02 10:02:46 -04:00
|
|
|
cannot kill itself.
|
2000-03-19 08:10:02 -05:00
|
|
|
|
|
|
|
It is also an error to call this function for a thread which is not running or
|
2003-06-14 12:55:35 -04:00
|
|
|
paused (in the latter case, the thread will be resumed first) -- if you do it,
|
2001-04-02 10:02:46 -04:00
|
|
|
a {\tt wxTHREAD\_NOT\_RUNNING} error will be returned.
|
1999-11-27 18:15:07 -05:00
|
|
|
|
1998-06-14 08:11:50 -04:00
|
|
|
\membersection{wxThread::OnExit}\label{wxthreadonexit}
|
|
|
|
|
|
|
|
\func{void}{OnExit}{\void}
|
|
|
|
|
2000-03-19 08:10:02 -05:00
|
|
|
Called when the thread exits. This function is called in the context of the
|
|
|
|
thread associated with the wxThread object, not in the context of the main
|
2002-01-16 01:28:11 -05:00
|
|
|
thread. This function will not be called if the thread was
|
2000-03-20 12:39:18 -05:00
|
|
|
\helpref{killed}{wxthreadkill}.
|
1998-06-14 08:11:50 -04:00
|
|
|
|
1999-11-27 18:15:07 -05:00
|
|
|
This function should never be called directly.
|
|
|
|
|
|
|
|
\membersection{wxThread::Pause}\label{wxthreadpause}
|
|
|
|
|
|
|
|
\func{wxThreadError}{Pause}{\void}
|
|
|
|
|
|
|
|
Suspends the thread. Under some implementations (Win32), the thread is
|
2002-01-16 01:28:11 -05:00
|
|
|
suspended immediately, under others it will only be suspended when it calls
|
1999-11-27 18:15:07 -05:00
|
|
|
\helpref{TestDestroy}{wxthreadtestdestroy} for the next time (hence, if the
|
|
|
|
thread doesn't call it at all, it won't be suspended).
|
|
|
|
|
|
|
|
This function can only be called from another thread context.
|
|
|
|
|
1999-01-25 13:33:08 -05:00
|
|
|
\membersection{wxThread::Run}\label{wxthreadrun}
|
|
|
|
|
|
|
|
\func{wxThreadError}{Run}{\void}
|
|
|
|
|
2002-01-16 01:28:11 -05:00
|
|
|
Starts the thread execution. Should be called after
|
1999-11-27 18:15:07 -05:00
|
|
|
\helpref{Create}{wxthreadcreate}.
|
|
|
|
|
|
|
|
This function can only be called from another thread context.
|
1999-01-25 13:33:08 -05:00
|
|
|
|
1998-06-14 08:11:50 -04:00
|
|
|
\membersection{wxThread::SetPriority}\label{wxthreadsetpriority}
|
|
|
|
|
|
|
|
\func{void}{SetPriority}{\param{int}{ priority}}
|
|
|
|
|
2001-07-19 16:47:12 -04:00
|
|
|
Sets the priority of the thread, between $0$ and $100$. It can only be set
|
2002-01-16 01:28:11 -05:00
|
|
|
after calling \helpref{Create()}{wxthreadcreate} but before calling
|
2001-07-19 16:47:12 -04:00
|
|
|
\helpref{Run()}{wxthreadrun}.
|
1998-06-14 08:11:50 -04:00
|
|
|
|
|
|
|
The following priorities are already defined:
|
|
|
|
|
|
|
|
\twocolwidtha{7cm}
|
|
|
|
\begin{twocollist}\itemsep=0pt
|
1998-07-17 08:34:50 -04:00
|
|
|
\twocolitem{{\bf WXTHREAD\_MIN\_PRIORITY}}{0}
|
|
|
|
\twocolitem{{\bf WXTHREAD\_DEFAULT\_PRIORITY}}{50}
|
|
|
|
\twocolitem{{\bf WXTHREAD\_MAX\_PRIORITY}}{100}
|
1998-06-14 08:11:50 -04:00
|
|
|
\end{twocollist}
|
1999-01-17 17:49:07 -05:00
|
|
|
|
|
|
|
\membersection{wxThread::Sleep}\label{wxthreadsleep}
|
|
|
|
|
1999-11-27 18:15:07 -05:00
|
|
|
\func{static void}{Sleep}{\param{unsigned long }{milliseconds}}
|
1999-01-17 17:49:07 -05:00
|
|
|
|
|
|
|
Pauses the thread execution for the given amount of time.
|
|
|
|
|
|
|
|
This function should be used instead of \helpref{wxSleep}{wxsleep} by all worker
|
2001-04-02 10:02:46 -04:00
|
|
|
threads (i.e. all except the main one).
|
1999-01-17 17:49:07 -05:00
|
|
|
|
1999-11-27 18:15:07 -05:00
|
|
|
\membersection{wxThread::Resume}\label{wxthreadresume}
|
|
|
|
|
|
|
|
\func{wxThreadError}{Resume}{\void}
|
|
|
|
|
|
|
|
Resumes a thread suspended by the call to \helpref{Pause}{wxthreadpause}.
|
|
|
|
|
|
|
|
This function can only be called from another thread context.
|
|
|
|
|
1999-12-06 07:31:04 -05:00
|
|
|
\membersection{wxThread::SetConcurrency}\label{wxthreadsetconcurrency}
|
|
|
|
|
|
|
|
\func{static bool}{SetConcurrency}{\param{size\_t }{level}}
|
|
|
|
|
|
|
|
Sets the thread concurrency level for this process. This is, roughly, the
|
|
|
|
number of threads that the system tries to schedule to run in parallel.
|
|
|
|
The value of $0$ for {\it level} may be used to set the default one.
|
|
|
|
|
2003-01-17 19:16:34 -05:00
|
|
|
Returns true on success or false otherwise (for example, if this function is
|
2003-06-14 12:55:35 -04:00
|
|
|
not implemented for this platform -- currently everything except Solaris).
|
1999-12-06 07:31:04 -05:00
|
|
|
|
1999-11-27 18:15:07 -05:00
|
|
|
\membersection{wxThread::TestDestroy}\label{wxthreadtestdestroy}
|
|
|
|
|
|
|
|
\func{bool}{TestDestroy}{\void}
|
|
|
|
|
2001-04-02 10:02:46 -04:00
|
|
|
This function should be called periodically by the thread to ensure that calls
|
1999-11-27 18:15:07 -05:00
|
|
|
to \helpref{Pause}{wxthreadpause} and \helpref{Delete}{wxthreaddelete} will
|
2003-01-17 19:16:34 -05:00
|
|
|
work. If it returns true, the thread should exit as soon as possible.
|
1999-11-27 18:15:07 -05:00
|
|
|
|
1999-01-17 17:49:07 -05:00
|
|
|
\membersection{wxThread::This}\label{wxthreadthis}
|
|
|
|
|
1999-11-27 18:15:07 -05:00
|
|
|
\func{static wxThread *}{This}{\void}
|
1999-01-17 17:49:07 -05:00
|
|
|
|
|
|
|
Return the thread object for the calling thread. NULL is returned if the calling thread
|
|
|
|
is the main (GUI) thread, but \helpref{IsMain}{wxthreadismain} should be used to test
|
|
|
|
whether the thread is really the main one because NULL may also be returned for the thread
|
2001-04-02 10:02:46 -04:00
|
|
|
not created with wxThread class. Generally speaking, the return value for such a thread
|
1999-01-17 17:49:07 -05:00
|
|
|
is undefined.
|
|
|
|
|
|
|
|
\membersection{wxThread::Yield}\label{wxthreadyield}
|
|
|
|
|
1999-11-27 18:15:07 -05:00
|
|
|
\func{void}{Yield}{\void}
|
1999-01-17 17:49:07 -05:00
|
|
|
|
|
|
|
Give the rest of the thread time slice to the system allowing the other threads to run.
|
|
|
|
See also \helpref{Sleep()}{wxthreadsleep}.
|
1999-01-25 13:33:08 -05:00
|
|
|
|
1999-11-27 18:15:07 -05:00
|
|
|
\membersection{wxThread::Wait}\label{wxthreadwait}
|
|
|
|
|
|
|
|
\constfunc{ExitCode}{Wait}{\void}
|
|
|
|
|
2000-07-15 15:51:35 -04:00
|
|
|
Waits until the thread terminates and returns its exit code or {\tt (ExitCode)-1} on error.
|
1999-11-27 18:15:07 -05:00
|
|
|
|
|
|
|
You can only Wait() for joinable (not detached) threads.
|
|
|
|
|
|
|
|
This function can only be called from another thread context.
|
2000-02-06 14:11:10 -05:00
|
|
|
|