To avoid jumps, the original version of the handler clears
the scroll flags. The method works well if a scroll gesture
continues, but it can preclude "coasting". The new version
adjusts the coordinates that determine the speed and direction
of scrolling.
ok shadchin@, mpi@
With the changes for multitouch input, new event types have been
introduced in wsmouse. There are separate types for contact count
and width values, and RESET events for controlling/stopping
pointer motion.
ok mpi@, shadchin@
Before:
Both drivers currently do one read(2) per event, but since we use a
"sync" event we have a least two of them for ws(4) but more commonly
3 for ws(4) and 4 for synaptics(4).
most of the code and ok mpi@
does not always report a 0 'w' value for two-finger contacts.
Diff from Ulf Brosziewski.
Fix a regression with Synaptics touchpads reported by Patrick keshishian
and Henrik Friedrichsen on misc@.
ok matthieu@, deraadt@
This improve "two-finger scrolling" on synaptics and will allow to
have proper "click-and-drag" support on elantech.
Note that this change is needed because wsmouse(4)/wscons(4) do not
support multitouch events for the moment and every protocol supported
by pms(4) do its own translation to fake such events.
From Ulf Brosziewski, ok shadchin@
