diff options
| author | donal.k.fellows@manchester.ac.uk <dkf> | 2007-10-29 16:04:11 (GMT) |
|---|---|---|
| committer | donal.k.fellows@manchester.ac.uk <dkf> | 2007-10-29 16:04:11 (GMT) |
| commit | 4a790ebd42e3ba4a893b31d0491ac478c4abb3dd (patch) | |
| tree | f1b13d0b63bdcb785dc2718534eb209b9796d50b /doc/CrtCmHdlr.3 | |
| parent | ef2f8a1261ee6fcabf5a88b9b099a93fb7eaeed6 (diff) | |
| download | tk-4a790ebd42e3ba4a893b31d0491ac478c4abb3dd.zip tk-4a790ebd42e3ba4a893b31d0491ac478c4abb3dd.tar.gz tk-4a790ebd42e3ba4a893b31d0491ac478c4abb3dd.tar.bz2 | |
Lots more GOOBE stuff. Now works with 'make html'!
Diffstat (limited to 'doc/CrtCmHdlr.3')
| -rw-r--r-- | doc/CrtCmHdlr.3 | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/doc/CrtCmHdlr.3 b/doc/CrtCmHdlr.3 index 7c050ec..a146447 100644 --- a/doc/CrtCmHdlr.3 +++ b/doc/CrtCmHdlr.3 @@ -4,7 +4,7 @@ '\" See the file "license.terms" for information on usage and redistribution '\" of this file, and for a DISCLAIMER OF ALL WARRANTIES. '\" -'\" RCS: @(#) $Id: CrtCmHdlr.3,v 1.2 2004/09/19 16:05:36 dkf Exp $ +'\" RCS: @(#) $Id: CrtCmHdlr.3,v 1.3 2007/10/29 16:04:12 dkf Exp $ '\" .so man.macros .TH Tk_CreateClientMessageHandler 3 "8.4" Tk "Tk Library Procedures" @@ -27,7 +27,7 @@ Procedure to invoke whenever a ClientMessage X event occurs on any display. .PP \fBTk_CreateClientMessageHandler\fR arranges for \fIproc\fR to be invoked -in the future whenever a ClientMessage X event occurs that isn't handled by +in the future whenever a ClientMessage X event occurs that is not handled by \fBWM_PROTOCOL\fR. \fBTk_CreateClientMessageHandler\fR is intended for use by applications which need to watch X ClientMessage events, such as drag and drop applications. @@ -49,7 +49,7 @@ The \fItkwin\fR parameter to \fIproc\fR is the Tk window which is associated with this event. \fIEventPtr\fR is a pointer to the X event. .PP Whenever an X ClientMessage event is processed by \fBTk_HandleEvent\fR, -the \fIproc\fR is called if it wasn't handled as a \fBWM_PROTOCOL\fR. +the \fIproc\fR is called if it was not handled as a \fBWM_PROTOCOL\fR. The return value from \fIproc\fR is normally 0. A non-zero return value indicates that the event is not to be handled further; that is, \fIproc\fR has done all processing that is to be |