summaryrefslogtreecommitdiff
path: root/Development/Documentation/PointerAccelerationAsOf16.mdwn
diff options
context:
space:
mode:
authorAlanCoopersmith <AlanCoopersmith@web>2013-08-25 15:06:22 -0700
committerxorg <iki-xorg@freedesktop.org>2013-08-25 15:06:22 -0700
commit091a512269ec2c39adb8824c8108e09cd11ef3ba (patch)
tree1cd8ae96352eff33747735654ab7197f46130721 /Development/Documentation/PointerAccelerationAsOf16.mdwn
parent8c3a1f433afd467ab499b56fa86410ae96744c00 (diff)
fix formatting after moin->iki conversion
Diffstat (limited to 'Development/Documentation/PointerAccelerationAsOf16.mdwn')
-rw-r--r--Development/Documentation/PointerAccelerationAsOf16.mdwn13
1 files changed, 3 insertions, 10 deletions
diff --git a/Development/Documentation/PointerAccelerationAsOf16.mdwn b/Development/Documentation/PointerAccelerationAsOf16.mdwn
index 12a7d94e..713ccab1 100644
--- a/Development/Documentation/PointerAccelerationAsOf16.mdwn
+++ b/Development/Documentation/PointerAccelerationAsOf16.mdwn
@@ -1,5 +1,3 @@
-
-
## Introduction
This documents the differences of the pointer acceleration in the X Server 1.6 vs. current (git master), and also serves to keep some info about this specific implementation, since some things changed substantially. The following holds for server 1.6:
@@ -52,15 +50,10 @@ Of course, more filters are computationally more intensive. Up to 8 are allowed
Specifies after how many milliseconds of inactivity non-visible state (i.e. subpixel position) is discarded. This affects three issues:
-1) Two mouse strokes do not have any effect on each other if they are
-
- * [[[VelocityReset|VelocityReset]]] miliseconds from each other. This would be neglible though.
-2) Velocity estimate remains correct within this time if the pointer/X is
-
- * stuck for a short moment, not querying the moving device.
-3) slow movements are guessed correctly if all device movement events are
+1. Two mouse strokes do not have any effect on each other if they are `VelocityReset` miliseconds from each other. This would be negligible though.
+2. Velocity estimate remains correct within this time if the pointer/X is stuck for a short moment, not querying the moving device.
+3. slow movements are guessed correctly if all device movement events are inside this time from each other. An increment might be neccessary to fully take advantage of adaptive deceleration.
- * inside this time from each other. An increment might be neccessary to fully take advantage of adaptive deceleration.
Default 300 ms.