diff options
author | jan.nijtmans <nijtmans@users.sourceforge.net> | 2022-06-20 22:00:42 (GMT) |
---|---|---|
committer | jan.nijtmans <nijtmans@users.sourceforge.net> | 2022-06-20 22:00:42 (GMT) |
commit | be7784afab2ddccb6b9195620dbbde40cb3f20a0 (patch) | |
tree | 8fc23d502ac4156d240746bf43deea14491578e0 /doc/Notifier.3 | |
parent | 6a68e8975e1f99854cd0bc04d2470984521b6051 (diff) | |
parent | 266b5c6fc2154bf97aece6d268187658590d0f8c (diff) | |
download | tcl-be7784afab2ddccb6b9195620dbbde40cb3f20a0.zip tcl-be7784afab2ddccb6b9195620dbbde40cb3f20a0.tar.gz tcl-be7784afab2ddccb6b9195620dbbde40cb3f20a0.tar.bz2 |
Merge 8.7
Diffstat (limited to 'doc/Notifier.3')
-rw-r--r-- | doc/Notifier.3 | 5 |
1 files changed, 1 insertions, 4 deletions
diff --git a/doc/Notifier.3 b/doc/Notifier.3 index e34e6ed..3b547ff 100644 --- a/doc/Notifier.3 +++ b/doc/Notifier.3 @@ -413,10 +413,7 @@ threads for those threads to be able to add events to its queue.) After adding an event to another thread's queue, you then typically need to call \fBTcl_ThreadAlert\fR to .QW "wake up" -that thread's notifier to alert it to the new event. Alternatively, -the queue positions \fBTCL_QUEUE_TAIL_ALERT_IF_EMPTY\fR and -\fBTCL_QUEUE_HEAD_ALERT_IF_EMPTY\fR can be used which automatically -call \fBTcl_ThreadAlert\fR if the thread's queue was empty. +that thread's notifier to alert it to the new event. .PP \fBTcl_DeleteEvents\fR can be used to explicitly remove one or more events from the event queue. \fBTcl_DeleteEvents\fR calls \fIproc\fR |