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

mention that wxPostEvent() only works for sending messages to the main thread

Browse Source 
git-svn-id: https://svn.wxwidgets.org/svn/wx/wxWidgets/trunk@28116 c3d73ce0-8a6f-49c7-b76d-6d57e0e08775
This commit is contained in:
Vadim Zeitlin
2004-06-30 23:28:10 +00:00
parent ed446867f5
commit 17b7cac5e8
1 changed files with 11 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

15
docs/latex/wx/tthreads.tex
View File

@@ -24,8 +24,9 @@ new thread for each new client), but in others it might be a very poor choice
(example: launching a separate thread when doing a long computation to show a (example: launching a separate thread when doing a long computation to show a
progress dialog). Other implementation choices are available: for the progress progress dialog). Other implementation choices are available: for the progress
dialog example it is far better to do the calculations in the dialog example it is far better to do the calculations in the
\helpref{idle handler}{wxidleevent} or call \helpref{wxYield()}{wxyield} \helpref{idle handler}{wxidleevent} or even simply do everything at once
periodically to update the screen. but call \helpref{wxWindow::Update()}{wxwindowupdate} periodically to update
the screen.
If you do decide to use threads in your application, it is strongly recommended If you do decide to use threads in your application, it is strongly recommended
that no more than one thread calls GUI functions. The thread sample shows that that no more than one thread calls GUI functions. The thread sample shows that
@@ -37,10 +38,16 @@ more robust and will undoubtedly save you countless problems (example: under
Win32 a thread can only access GDI objects such as pens, brushes, \&c created by Win32 a thread can only access GDI objects such as pens, brushes, \&c created by
itself and not by the other threads). itself and not by the other threads).
For communication between threads, use For communication between secondar threads and the main thread, use may use
\helpref{wxEvtHandler::AddPendingEvent}{wxevthandleraddpendingevent} \helpref{wxEvtHandler::AddPendingEvent}{wxevthandleraddpendingevent}
or its short version \helpref{wxPostEvent}{wxpostevent}. These functions or its short version \helpref{wxPostEvent}{wxpostevent}. These functions
have thread safe implementation so that they can be used as they are for have thread safe implementation so that they can be used as they are for
sending event from one thread to another. sending event from one thread to another. However there is no built in method
to send messages to the worker threads and you will need to use the available
synchronization classes to implement the solution which suits your needs
yourself. In particular, please notice that it is \emph{not} enough to derive
your class from \helpref{wxThread}{wxthread} and
\helpref{wxEvtHandler}{wxevthandler} to send messages to it: in fact, this does
\emph{not} work at all.