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

Minor clarification

Browse Source 
git-svn-id: https://svn.wxwidgets.org/svn/wx/wxWidgets/trunk@53410 c3d73ce0-8a6f-49c7-b76d-6d57e0e08775
This commit is contained in:
Robert Roebling
2008-04-29 09:53:36 +00:00
parent 1c13f06e4e
commit 36a2d2c43e
2 changed files with 5 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
docs/doxygen/overviews/thread.h
View File

@@ -45,7 +45,7 @@ Win32 a thread can only access GDI objects such as pens, brushes, c created by
itself and not by the other threads).
For communication between secondary threads and the main thread, you may use
wxEvtHandler::AddPendingEvent or its short version wxPostEvent. These functions
wxEvtHandler::QueueEvent or its short version ::wxQueueEvent. These functions
have a thread-safe implementation so that they can be used as they are for
sending events 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

8
interface/event.h
View File

@@ -292,12 +292,12 @@ public:
@code
void FunctionInAWorkerThread(const wxString& str)
{
wxCommandEvent * const e = new wxCommandEvent;
wxCommandEvent* evt = new wxCommandEvent;
// NOT e->SetString(str) as this would be a shallow copy
e->SetString(str.c_str()); // make a deep copy
// NOT evt->SetString(str) as this would be a shallow copy
evt->SetString(str.c_str()); // make a deep copy
wxTheApp->QueueEvent(new wxCommandEvent
wxTheApp->QueueEvent( evt );
}
@endcode