| Age | Commit message (Collapse) | Author |
|---|
|
HistorySize is now deprecated for ABI > 0, so list it as a removed option in
the man page.
X.Org Bug 18988 <http://bugs.freedesktop.org/show_bug.cgi?id=18988>
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
Signed-off-by: Christoph Brill <egore911@egore911.de>
Signed-off-by: Henrik Rydberg <rydberg@euromail.se>
(cherry picked from commit 8d5cf39e7f37ce78aaec423a9da397d72b1629d2)
|
|
If RightEdge is specified as a config option, ignore the SpecialScrollArea.
Otherwise, adjust right_edge to the bounds of the hardware scroll area.
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
Signed-off-by: Christoph Brill <egore911@egore911.de>
Signed-off-by: Henrik Rydberg <rydberg@euromail.se>
(cherry picked from commit 0f2802726fe7374afeca7447e3127bc1d7f3247c)
|
|
|
|
If Protocol event is used, the driver initializes defaults based on the
capabilities reported by the kernel driver. Acceleration and edges are based
on the dimensions reported by the kernel. If the kernel reports multi-finger
detection, two-finger vertical scrolling is enabled, horizontal two-finger
scrolling is disabled and edge scrolling is disabled. If no multi-finger
capabilities are reported, edge scrolling is enabled for both horizontal and
vertical scrolling.
|
|
|
|
Remove the repeater functionality completely from the synaptics touchpad
driver. It is buggy in its current implementation and its usefulness is
questionable.
According to the INSTALL file, the repeater is there only for testing. In
fact, if a supported device is found even a configured repeater fifo is
automatically disabled. For most users the functionality is therefore
irrelevant and can be confusing. If I understand the workings of the
repeater correctly, a developer could instead just read the data directly
from an unsupported device's character special file under /dev
or /dev/input.
With today's more dynamic device configuration possibilities via udev and
hal it's also less likely that the synaptics driver would silently block
another devices data, this situation being for what the repeater
functionality seems to have been introduced in the past.
Signed-off-by: Peter Hutterer <peter.hutterer@redhat.com>
|
|
|
|
|
|
This adds 3 new options. Use them as follows:
Section "InputDevice"
...
Option "ClickFinger1" "1"
Option "ClickFinger2" "3"
Option "ClickFinger3" "2"
EndSection
The driver would then report:
* clicking one finger = left click
* clicking with two fingers = right click
* clicking with 3 fingers = middle mouse button
|
|
This uses the facilities to build the drivers man page to also build the
two configuration programs.
|
|
|
|
This also points out to the new "Path" option in the man page
|
|
Many of the files contain redundant information. The plan is to remove most of
the (maybe even all) and add the content to the man page.
|
|
This version is able to build against latest xorg git (including xinput
changes for MPX). It incoperates many concepts stolen from xf86-input-evdev.
I'm not sure about *BSD support, but from what I understood psmcomm is only
used on *BSD whild eventcomm is only used on Linux. So I enabled the build
of these only on the given operating system. Also fix some minor issues that
are related to the old build system (VERSION_ID related).
|
|
I forgot to add these when copying over the build system from xf86-input-evdev.
|
|
This way it is similar to the structure of the xf86-input-evdev driver.
|
