\fBButton3, B3\fR \fBAlt\fR
\fBButton4, B4\fR \fBDouble\fR
\fBButton5, B5\fR \fBTriple\fR
-\fBMod1, M1\fR
+\fBMod1, M1\fR \fBQuadruple\fR
.DE
Where more than one value is listed, separated by commas, the values
are equivalent.
is associated with the alt key(s) on the keyboard (keysyms
\fBAlt_L\fR and \fBAlt_R\fR).
.PP
-The \fBDouble\fR and \fBTriple\fR modifiers are a convenience
-for specifying double mouse clicks and other repeated
-events. They cause a particular event pattern to be
-repeated 2 or 3 times, and also place a time and space requirement
-on the sequence: for a sequence of events to match a \fBDouble\fR
-or \fBTriple\fR pattern, all of the events must occur close together
-in time and without substantial mouse motion in between.
-For example, \fB<Double-Button-1>\fR
-is equivalent to \fB<Button-1><Button-1>\fR with the extra
-time and space requirement.
+The \fBDouble\fR, \fBTriple\fR and \fBQuadruple\fR modifiers are a
+convenience for specifying double mouse clicks and other repeated
+events. They cause a particular event pattern to be repeated 2, 3 or 4
+times, and also place a time and space requirement on the sequence: for a
+sequence of events to match a \fBDouble\fR, \fBTriple\fR or \fBQuadruple\fR
+pattern, all of the events must occur close together in time and without
+substantial mouse motion in between. For example, \fB<Double-Button-1>\fR
+is equivalent to \fB<Button-1><Button-1>\fR with the extra time and space
+requirement.
.SH "EVENT TYPES"
.PP
couple non-standard X event types that were added to better support
the Macintosh and Windows platforms. Below is a list of all the valid
types; where two names appear together, they are synonyms.
-.DS C
+.DS
.ta 5c 10c
-\fBActivate Enter Map
-ButtonPress, Button Expose Motion
-.VS
-ButtonRelease FocusIn MouseWheel
-.VE
-Circulate FocusOut Property
+\fBActivate Destroy Map
+ButtonPress, Button Enter MapRequest
+ButtonRelease Expose Motion
+Circulate FocusIn MouseWheel
+CirculateRequest FocusOut Property
Colormap Gravity Reparent
-Configure KeyPress, Key Unmap
-Deactivate KeyRelease Visibility
-Destroy Leave\fR
+Configure KeyPress, Key ResizeRequest
+ConfigureRequest KeyRelease Unmap
+Create Leave Visibility
+Deactivate\fR
.DE
.PP
.VS
NotifyInferior NotifyPointerRoot
NotifyNonlinear NotifyVirtual\fR
.DE
+For \fBConfigureRequest\fR events, the string will be one of:
+.DS
+.ta 6c
+\fBAbove Opposite
+Below None
+BottomIf TopIf\fR
+.DE
For events other than these, the substituted string is undefined.
.RE
.IP \fB%f\fR 5
for \fBEnter\fR and \fBLeave\fR events.
.IP \fB%h\fR 5
.VS
-The \fIheight\fR field from the event. Valid for the \fBConfigure\fR and
+The \fIheight\fR field from the event. Valid for the \fBConfigure\fR,
+\fBConfigureRequest\fR, \fBCreate\fR, \fBResizeRequest\fR, and
\fBExpose\fR events.
.VE
+.IP \fB%i\fR 5
+The \fIwindow\fR field from the event, represented as a hexadecimal
+integer.
.IP \fB%k\fR 5
The \fIkeycode\fR field from the event. Valid only for \fBKeyPress\fR
and \fBKeyRelease\fR events.
.IP \fB%p\fR 5
The \fIplace\fR field from the event, substituted as one of the
strings \fBPlaceOnTop\fR or \fBPlaceOnBottom\fR. Valid only
-for \fBCirculate\fR events.
+for \fBCirculate\fR and \fBCirculateRequest\fR events.
.IP \fB%s\fR 5
The \fIstate\fR field from the event. For \fBButtonPress\fR,
\fBButtonRelease\fR, \fBEnter\fR, \fBKeyPress\fR, \fBKeyRelease\fR,
.IP \fB%w\fR 5
The \fIwidth\fR field from the event. Valid only for
.VS
-\fBConfigure\fR and \fBExpose\fR events.
+\fBConfigure\fR, \fBConfigureRequest\fR, \fBCreate\fR,
+\fBResizeRequest\fR, and \fBExpose\fR events.
.VE
.IP \fB%x\fR 5
The \fIx\fR field from the event. Valid only for events containing
The \fIy\fR field from the event. Valid only for events containing
a \fIy\fR field.
.IP \fB%A\fR 5
-Substitutes the ASCII character corresponding to the event, or
-the empty string if the event doesn't correspond to an ASCII character
-(e.g. the shift key was pressed). \fBXLookupString\fR does all the
-work of translating from the event to an ASCII character.
+Substitutes the UNICODE character corresponding to the event, or
+the empty string if the event doesn't correspond to a UNICODE character
+(e.g. the shift key was pressed). \fBXmbLookupString\fR (or
+\fBXLookupString\fR when input method support is turned off) does all
+the work of translating from the event to a UNICODE character.
Valid only for \fBKeyPress\fR and \fBKeyRelease\fR events.
.IP \fB%B\fR 5
The \fIborder_width\fR field from the event. Valid only for
-\fBConfigure\fR events.
+\fBConfigure\fR, \fBConfigureRequest\fR, and \fBCreate\fR events.
.VS
.IP \fB%D\fR 5
This reports the \fIdelta\fR value of a \fBMouseWheel\fR event. The
If the extra backslash hadn't been added, Tcl would not have been
able to parse the script correctly.
-.SH MULTIPLE MATCHES
+.SH "MULTIPLE MATCHES"
.PP
It is possible for several bindings to match a given X event.
If the bindings are associated with different \fItag\fR's,
If the \fBbreak\fR command is invoked within a binding script,
then that script terminates and no other scripts will be invoked
for the event.
-.VS
.PP
If more than one binding matches a particular event and they
have the same \fItag\fR, then the most specific binding
(c) if the modifiers specified in one pattern are a subset of the
modifiers in another pattern, then the pattern with more modifiers
is more specific.
-.VS
(d) a virtual event whose physical pattern matches the sequence is less
specific than the same physical pattern that is not associated with a
virtual event.
will be invoked, but if the user presses button 2 then one of
either the \fB<<Paste>>\fR or the \fB<<Scroll>>\fR bindings will
be invoked, but exactly which one gets invoked is undefined.
-.VE
.PP
If an X event does not match any of the existing bindings, then the
event is ignored.
(outside the context of any Tcl procedure).
.SH "SEE ALSO"
-bgerror
+bgerror, keysyms
.SH KEYWORDS
form, manual
-
OSDN Git Service
