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

Expanded comment in Initialize to include why Initialize is needed on OS X

Browse Source 
git-svn-id: https://svn.wxwidgets.org/svn/wx/wxWidgets/trunk@29673 c3d73ce0-8a6f-49c7-b76d-6d57e0e08775
This commit is contained in:
Kevin Hock
2004-10-06 16:25:33 +00:00
parent 7725dc7c0a
commit e59461fff5
1 changed files with 5 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
src/common/socket.cpp
View File

@@ -132,6 +132,11 @@ bool wxSocketBase::Initialize()
BTW, the main thread must not be stopped using sleep or block BTW, the main thread must not be stopped using sleep or block
on a semaphore (a bad idea in any case) or socket operations on a semaphore (a bad idea in any case) or socket operations
will time out. will time out.
On the Mac side, Initialize() stores a pointer to the CFRunLoop for
the main thread. Because secondary threads do not have run loops,
adding event notifications to the "Current" loop would have no
effect at all, events would never fire.
*/ */
wxASSERT_MSG( wxIsMainThread(), wxASSERT_MSG( wxIsMainThread(),
wxT("Call wxSocketBase::Initialize() from the main thread first!")); wxT("Call wxSocketBase::Initialize() from the main thread first!"));