On Mon, Jun 15, 2015 at 10:56:21AM -0700, Bill Spitzak wrote:
> My idea is that there still would be an indication of "fake resolution",
> but when that is turned on it also fills in the resolution values with this
> value as a guess. Then anything that fails to test the fake resolution flag
> woul
My idea is that there still would be an indication of "fake resolution",
but when that is turned on it also fills in the resolution values with this
value as a guess. Then anything that fails to test the fake resolution flag
would at least tend to produce stuff the same size as this does. It does
s
please fix your email client to not drop CC's on reply.
On Sat, Jun 13, 2015 at 09:30:35AM -0700, Bill Spitzak wrote:
> Can you set the "fake" resolution so that you get the same answer without
> having to check if it is fake?
>
> It looks like setting tp->device->abs.absinfo_x/y->resolution to d
Can you set the "fake" resolution so that you get the same answer
without having to check if it is fake?
It looks like setting tp->device->abs.absinfo_x/y->resolution to
diagonal * 2 / DEFAULT_HYSTERESIS_MARGIN_DENOMINATOR would avoid the if
statement, and I would probably make everything that
Hi,
On 12-06-15 08:09, Peter Hutterer wrote:
Some touchpads, e.g. the Cyapa in the Acer c720 have a small axis range
([0, 870], [0, 470]), so the diagonal/magic value yields a hysteresis margin
of 1 device unit. On that device, that's one-tenth of a millimeter, causing
pointer motion just by hol
Some touchpads, e.g. the Cyapa in the Acer c720 have a small axis range
([0, 870], [0, 470]), so the diagonal/magic value yields a hysteresis margin
of 1 device unit. On that device, that's one-tenth of a millimeter, causing
pointer motion just by holding the finger.
For touchpads that provide a p
