Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
-
CMutex Question
>>The 10 is important, otherwise this statements blocks the execution >Actually it just waits for the other thread to realease the lock, with no param you just wait forever. That is correct. If you block forever, the next lines of code wouldn't make any sense. >Oh, and another thing. Do you...- chr123
- Post #5
- Forum: Microsoft: Visual C++
-
CMutex Question
Ok, got it! The trick is to switch the statements (more or less): // Ensure exclusive execution CMutex *oMttx = new CMutex(FALSE, "MUTEST"); CSingleLock singleLock(oMttx, FALSE); singleLock.Lock(10); // The 10 is important, otherwise this statements blocks the execution, until...- chr123
- Post #2
- Forum: Microsoft: Visual C++
-
CMutex Question
The question is simple: Why doesn't show up a message box? The operation ("do") startet in MyControllingFunction is lengthy. So all new threads are started in parallel. The mutexes are created in different threads, but should all refer to the same kernel object. What point am I missing...- chr123
- Thread
- Replies: 7
- Forum: Microsoft: Visual C++
