summaryrefslogtreecommitdiff
path: root/man/synaptics.man
diff options
context:
space:
mode:
authorPeter Hutterer <peter.hutterer@who-t.net>2009-07-22 10:41:08 +1000
committerPeter Hutterer <peter.hutterer@who-t.net>2009-07-27 11:27:27 +1000
commitd7a4a63d1d67bf38a7948722881de8d926319c6c (patch)
tree7a3caccdfa89b5750a5b137c2f4b39eb91460804 /man/synaptics.man
parent7179a0eb11a842d9d5a420f5702a411b0dc217a2 (diff)
Revert "Auto-adjust edges if values fall outside queried min/max ranges. (#21001)"
This reverts commit afb60a0b2497c5d08cbd1739fa8ae6585c428881. From comment 24 to #21001: I've been running this code for over a week now and I'm not happy with it. Once I move over to the right, the scroll-edge becomes so small that it's hard to trigger. Source of the problem is the information provided by the kernel. The kernel hands us a min/max value for the synaptics pads but this value is not reflective of the actual physical boundaries. The other dimensions are based on these min/max ranges. My RightEdge setting by default is 5129, after moving to the right it becomes 5677. The announced max for x is 5472. We have model-specific edge settings and in the case of synaptics the width of the scroll area is 7% of the total width (based on min/max). This works, but obviously only because the max is wrong. I've tried upping this to 15% and it works fine but unless the edge is adjusted the scroll bar takes over too much of the pad. So right now I'm inclined to revert this patch and just ditch any auto-adjustment of scroll edges whatsoever. This way, the original setting is maintained even if we reach outside of the min/max area. Conflicts: src/synaptics.c Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
Diffstat (limited to 'man/synaptics.man')
-rw-r--r--man/synaptics.man17
1 files changed, 7 insertions, 10 deletions
diff --git a/man/synaptics.man b/man/synaptics.man
index 9d30a20..86be548 100644
--- a/man/synaptics.man
+++ b/man/synaptics.man
@@ -99,7 +99,9 @@ option is not needed with synaptics 1.0 or later. See section
X coordinate for left edge. Property: "Synaptics Edges"
.TP 7
.BI "Option \*qRightEdge\*q \*q" integer \*q
-X coordinate for right edge. Property: "Synaptics Edges"
+X coordinate for right edge. If this option is set,
+.BI SpecialScrollAreaRight
+is ignored. Property: "Synaptics Edges"
.TP 7
.BI "Option \*qTopEdge\*q \*q" integer \*q
Y coordinate for top edge. Property: "Synaptics Edges"
@@ -107,6 +109,10 @@ Y coordinate for top edge. Property: "Synaptics Edges"
.BI "Option \*qBottomEdge\*q \*q" integer \*q
Y coordinate for bottom edge. Property: "Synaptics Edges"
.TP 7
+.BI "Option \*qSpecialScrollAreaRight\*q \*q" boolean \*q
+Some touchpads have a scroll region on the right edge. Disable this option if
+you have one but don't want use it as scroll wheel region.
+.TP 7
.BI "Option \*qFingerLow\*q \*q" integer \*q
When finger pressure drops below this value, the driver counts it as a
release. Property: "Synaptics Finger"
@@ -894,11 +900,6 @@ Tapping is disabled by default for touchpads with one or more physical buttons.
To enable it you need to map tap actions to buttons. See the "TapButton1",
"TapButton2" and "TapButton3" options.
.LP
-Some devices report min/max values but provide values outside this range.
-In this case, the driver auto-adjusts the edge values. Acceleration and
-speed values are not affected. User-specified edges are not
-auto-adjusted.
-.LP
Button mapping for physical buttons is handled in the server.
If the device is switched to left-handed (an in-server mapping of physical
buttons 1, 2, 3 to the logical buttons 3, 2, 1, respectively), both physical
@@ -911,10 +912,6 @@ The following options are no longer part of the driver configuration:
.BI "Option \*qRepeater\*q \*q" string \*q
.TP
.BI "Option \*qHistorySize\*q \*q" integer \*q
-.TP 7
-.BI "Option \*qSpecialScrollAreaRight\*q \*q" boolean \*q
-Some touchpads have a scroll region on the right edge. Disable this option if
-you have one but don't want use it as scroll wheel region.
.SH "AUTHORS"
.LP