On Thu, 2 Aug 2018, 09:14 Peter Hutterer, wrote:
>
> nah, not without scaling. The device always reports in integers only, but
> those integers have a physical reference point - the resolution of the
> device in DPI.
Ah right I understand now!
Thanks for your time and sorry about the noise. :)
On Thu, Aug 02, 2018 at 08:20:38AM +0200, Josh Simmons wrote:
> On Thu, Aug 2, 2018 at 7:49 AM, Peter Hutterer
> wrote:
> >
> > and since devices don't give you anything < 1 unit delta, subpixel isn't
> > really a thing unless you lower the speed setting.
> >
>
> So perhaps I'm missing something
On Thu, Aug 2, 2018 at 7:49 AM, Peter Hutterer wrote:
>
> and since devices don't give you anything < 1 unit delta, subpixel isn't
> really a thing unless you lower the speed setting.
>
So perhaps I'm missing something, but the raw events as reported by
libinput debug-events do in fact have sub-u
On Tue, Jul 31, 2018 at 07:48:46PM +0200, Josh Simmons wrote:
> Hello there,
>
> I've found what seems to be some interesting behaviour in the events
> returned from xinput2 while using the libinput driver with the "FLAT"
> profile.
the "flat" profile disables acceleration, so what comes out of t
Hello there,
I've found what seems to be some interesting behaviour in the events
returned from xinput2 while using the libinput driver with the "FLAT"
profile.
It seems that changing the sensitivity (via the gnome control panel)
only changes the scale of the events sent by libinput, and not the
