Home | All Classes | Main Classes | Annotated | Grouped Classes | Functions |
The TQWaitCondition class allows waiting/waking for conditions between threads. More...
All the functions in this class are thread-safe when TQt is built with thread support.
#include <qwaitcondition.h>
TQWaitConditions allow a thread to tell other threads that some sort of condition has been met; one or many threads can block waiting for a TQWaitCondition to set a condition with wakeOne() or wakeAll(). Use wakeOne() to wake one randomly selected event or wakeAll() to wake them all. For example, say we have three tasks that should be performed every time the user presses a key; each task could be split into a thread, each of which would have a run() body like this:
TQWaitCondition key_pressed; for (;;) { key_pressed.wait(); // This is a TQWaitCondition global variable // Key was pressed, do something interesting do_something(); }
A fourth thread would read key presses and wake the other three threads up every time it receives one, like this:
TQWaitCondition key_pressed; for (;;) { getchar(); // Causes any thread in key_pressed.wait() to return from // that method and continue processing key_pressed.wakeAll(); }
Note that the order the three threads are woken up in is undefined, and that if some or all of the threads are still in do_something() when the key is pressed, they won't be woken up (since they're not waiting on the condition variable) and so the task will not be performed for that key press. This can be avoided by, for example, doing something like this:
TQMutex mymutex; TQWaitCondition key_pressed; int mycount=0; // Worker thread code for (;;) { key_pressed.wait(); // This is a TQWaitCondition global variable mymutex.lock(); mycount++; mymutex.unlock(); do_something(); mymutex.lock(); mycount--; mymutex.unlock(); } // Key reading thread code for (;;) { getchar(); mymutex.lock(); // Sleep until there are no busy worker threads while( mycount > 0 ) { mymutex.unlock(); sleep( 1 ); mymutex.lock(); } mymutex.unlock(); key_pressed.wakeAll(); }
The mutexes are necessary because the results of two threads attempting to change the value of the same variable simultaneously are unpredictable.
See also Environment Classes and Threading.
See also wakeOne() and wakeAll().
Release the locked mutex and wait on the thread event object. The mutex must be initially locked by the calling thread. If mutex is not in a locked state, this function returns immediately. If mutex is a recursive mutex, this function returns immediately. The mutex will be unlocked, and the calling thread will block until either of these conditions is met:
The mutex will be returned to the same locked state. This function is provided to allow the atomic transition from the locked state to the wait state.
See also wakeOne() and wakeAll().
See also wakeOne().
See also wakeAll().
This file is part of the TQt toolkit. Copyright © 1995-2007 Trolltech. All Rights Reserved.
Copyright © 2007 Trolltech | Trademarks | TQt 3.3.8
|