Hello Peter,
I'm really sorry. I somehow completely missed your email.
I have now tested your patch with the 1.10-branch of libinput and
xf86-input-libinput-0.27.1 (the current versions used on my Arch Linux
PC).
Therefore I patched xf86-input-libinput.c like that:
diff --git a/src/xf86libinput.c
On Wed, Jan 31, 2018 at 1:02 AM, Peter Hutterer
wrote:
> On Tue, Jan 30, 2018 at 04:18:26PM +1000, Peter Hutterer wrote:
>> On Wed, Jan 24, 2018 at 10:47:10AM +0100, Johannes Pointner wrote:
>> > On Wed, Jan 24, 2018 at 10:18 AM, Peter Hutterer
>> > wrote:
>>
On Wed, Jan 24, 2018 at 10:18 AM, Peter Hutterer
wrote:
> On Wed, Jan 24, 2018 at 10:04:52AM +0100, Johannes Pointner wrote:
>> Hello,
>>
>> I have noticed that since we are using xf86-input-libinput all our
>> touchscreens (resistive and pcap) reporting a value
Hello,
I have noticed that since we are using xf86-input-libinput all our
touchscreens (resistive and pcap) reporting a value of 15 for
maxTouchPoints.
After further looking into this I saw that xf86-input-libinput sets
this value fix to 15. I also checked if it is possible to get this
info from l
