From 36a2d2c43e3a7e5fa58dae3fa56a3d49c7906de3 Mon Sep 17 00:00:00 2001 From: Robert Roebling Date: Tue, 29 Apr 2008 09:53:36 +0000 Subject: [PATCH] Minor clarification git-svn-id: https://svn.wxwidgets.org/svn/wx/wxWidgets/trunk@53410 c3d73ce0-8a6f-49c7-b76d-6d57e0e08775 --- docs/doxygen/overviews/thread.h | 2 +- interface/event.h | 8 ++++---- 2 files changed, 5 insertions(+), 5 deletions(-) diff --git a/docs/doxygen/overviews/thread.h b/docs/doxygen/overviews/thread.h index 37b6d2ae30..2734495583 100644 --- a/docs/doxygen/overviews/thread.h +++ b/docs/doxygen/overviews/thread.h @@ -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 diff --git a/interface/event.h b/interface/event.h index 1b74689488..4527139b10 100644 --- a/interface/event.h +++ b/interface/event.h @@ -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 -- 2.45.2