From: Kevin Hock <hockkn@yahoo.com>
Date: Wed, 6 Oct 2004 16:25:33 +0000 (+0000)
Subject: Expanded comment in Initialize to include why Initialize is needed on OS X
X-Git-Url: https://git.saurik.com/wxWidgets.git/commitdiff_plain/e59461fff579fcffaaf97baabcfc9f7504e4fed6?ds=inline

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


git-svn-id: https://svn.wxwidgets.org/svn/wx/wxWidgets/trunk@29673 c3d73ce0-8a6f-49c7-b76d-6d57e0e08775
---

diff --git a/src/common/socket.cpp b/src/common/socket.cpp
index eb955def01..4d98262d30 100644
--- a/src/common/socket.cpp
+++ b/src/common/socket.cpp
@@ -132,6 +132,11 @@ bool wxSocketBase::Initialize()
             BTW, the main thread must not be stopped using sleep or block
             on a semaphore (a bad idea in any case) or socket operations
             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(),
             wxT("Call wxSocketBase::Initialize() from the main thread first!"));