On Wed, Apr 07, 2010 at 10:27:03PM +0100, Matthew Garrett wrote:
> On Wed, Apr 07, 2010 at 05:14:32PM -0400, Jon Masters wrote:
>
> > What would be the correct way to enable synclient support? I didn't find
> > any documentation so had to go poking to figure out the "right" thing.
>
> Don't use synclient. Use xinput.
synclient uses the same backend approach as xinput does and it is "safe" to
use. It uses device properties since 1.1 (F-12)by default and the
commandline-option to force the use of SHM was removed in 1.2 (F-12).
In F12, Jon's option has zero effect on the use of synclient.
xinput is IMO too generic to be really user-friendly, especially since you
still need to figure out what property to trigger. Similar options may be
bunched together in one property so you need to make sure you don't
overwrite the other options.
As an example, to set one-finger tapping you need to run:
xinput --set-prop "Synaptics Touchpad" "Synaptics Tap Actions" 0 0 0 0 1 0 0
substituting the zeros with whatever value was there before to avoid
changing another option.
With synclient, the same is
synclient TapButton1=1
In both cases, the request sent to the server is identical, or should be
anyway. I recommend the use of synclient to users testing the driver for
that reason, xinput is the generic swiss property knife.
Jon:
there's a synaptics configuration tab in system-preferences-mouse for
the most common settings including the option to turn tapping on or off (off
should actually be the default, not sure why it wasn't on your box).
Cheers,
Peter
--
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/devel
