summaryrefslogtreecommitdiffstats
path: root/doc/bind.n
diff options
context:
space:
mode:
authormarc_culler <marc.culler@gmail.com>2023-11-27 15:31:55 (GMT)
committermarc_culler <marc.culler@gmail.com>2023-11-27 15:31:55 (GMT)
commitc60d0f8978d1ebd2ec490caa1464b450c70b9d9f (patch)
tree0621b90d234f438e570f1d01a1b33bff5ff1ed4a /doc/bind.n
parent86bb88b4cfed28625b8dfadb202c7f86d2531ec3 (diff)
downloadtk-c60d0f8978d1ebd2ec490caa1464b450c70b9d9f.zip
tk-c60d0f8978d1ebd2ec490caa1464b450c70b9d9f.tar.gz
tk-c60d0f8978d1ebd2ec490caa1464b450c70b9d9f.tar.bz2
Introduce a separate TouchpadScroll event. Avoids Extended-MouseWheel events being handled by MouseWheel bindings.
Diffstat (limited to 'doc/bind.n')
-rw-r--r--doc/bind.n20
1 files changed, 10 insertions, 10 deletions
diff --git a/doc/bind.n b/doc/bind.n
index 72129d8..518d522 100644
--- a/doc/bind.n
+++ b/doc/bind.n
@@ -173,11 +173,11 @@ types; where two names appear together, they are synonyms.
\fBButton\fR, \fBButtonPress\fR \fBEnter\fR \fBMapRequest\fR
\fBButtonRelease\fR \fBExpose\fR \fBMotion\fR
\fBCirculate\fR \fBFocusIn\fR \fBMouseWheel\fR
-\fBCirculateRequest\fR \fBFocusOut\fR \fBProperty\fR
-\fBColormap\fR \fBGravity\fR \fBReparent\fR
-\fBConfigure\fR \fBKey\fR, \fBKeyPress\fR \fBResizeRequest\fR
-\fBConfigureRequest\fR \fBKeyRelease\fR \fBUnmap\fR
-\fBCreate\fR \fBLeave\fR \fBVisibility\fR
+\fBTouchpadScroll\fR \fBCirculateRequest\fR \fBFocusOut\fR
+\fBProperty\fR \fBColormap\fR \fBGravity\fR
+\fBReparent\fR \fBConfigure\fR \fBKey\fR, \fBKeyPress\fR
+\fBResizeRequest\fR \fBConfigureRequest\fR \fBKeyRelease\fR
+\fBUnmap\fR \fBCreate\fR \fBLeave\fR \fBVisibility\fR
\fBDeactivate\fR
.DE
Most of the above events have the same fields and behaviors as events
@@ -198,7 +198,7 @@ active. Likewise, the \fBDeactive\fR event is sent when the window's
state changes from active to deactive. There are no useful percent
substitutions you would make when binding to these events.
.IP \fBMouseWheel\fR 5
-Many contemporary mice support a mouse wheel, which is used
+Many contemporary mice include a mouse wheel, which is used
for scrolling documents without using the scrollbars. By rolling the
wheel, the system will generate \fBMouseWheel\fR events that the
application can use to scroll. The event is routed to the
@@ -216,19 +216,19 @@ Horizontal scrolling uses \fBShift-MouseWheel\fR events, with positive
negative right scrolling. Horizontal scrolling events are generated
tilt wheels on some mice. Horizontal scrolling can also be emulated
by holding Shift and scrolling vertically.
-.PP
+.RE
+.IP "\fBTouchpadScroll\fR" 5
On some platforms (currently Windows and macOS) there is support for
high-resolution scrolling devices, such as touchpads. This is
-provided via \fBExtended-MouseWheel\fR events. These events store two
+provided via \fBTouchpadScroll\fR events. These events store two
16 bit delta values in the integer provided by the \fB%D\fR
-subsstitution. The \fIX\fR delta is in the high order 16 bits and the
+substitution. The \fIX\fR delta is in the high order 16 bits and the
\fIY\fR delta is in the low order 16 bits. These values can be
unpacked by using the tk::PreciseScrollDeltas utility procedure. For
example:
.CS
lassign [tk::PreciseScrollDeltas %D] deltaX deltaY
.CE
-.RE
.IP "\fBKeyPress\fR, \fBKeyRelease\fR" 5
The \fBKeyPress\fR and \fBKeyRelease\fR events are generated
whenever a key is pressed or released. \fBKeyPress\fR and \fBKeyRelease\fR