From fc4fe30871fad3e3957c299838f3eba5ddb9e3b5 Mon Sep 17 00:00:00 2001
From: Vadim Zeitlin <vadim@wxwidgets.org>
Date: Thu, 17 Jul 2003 22:42:36 +0000
Subject: [PATCH] describe better how to use ssociated mutex

git-svn-id: https://svn.wxwidgets.org/svn/wx/wxWidgets/trunk@22065 c3d73ce0-8a6f-49c7-b76d-6d57e0e08775
---
 docs/latex/wx/conditn.tex | 8 ++++++--
 1 file changed, 6 insertions(+), 2 deletions(-)

diff --git a/docs/latex/wx/conditn.tex b/docs/latex/wx/conditn.tex
index 42fef3052e..52dfc70846 100644
--- a/docs/latex/wx/conditn.tex
+++ b/docs/latex/wx/conditn.tex
@@ -13,8 +13,12 @@ worker threads it already makes much more sense).
 
 Note that a call to \helpref{Signal()}{wxconditionsignal} may happen before the
 other thread calls \helpref{Wait()}{wxconditionwait} and, just as with the
-pthread conditions, the signal is then lost and so if you want to be sure to
-get it you must use a mutex together with the condition variable.
+pthread conditions, the signal is then lost and so if you want to be sure that
+you don't miss it you must keep the mutex associated with the condition
+initially locked and lock it again before calling 
+\helpref{Signal()}{wxconditionsignal}. Of course, this means that this call is
+going to block until \helpref{Wait()}{wxconditionwait} is called by another
+thread.
 
 \wxheading{Example}
 
-- 
2.50.0

