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:04:52A
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:04:52AM +0100, Johannes Pointner wrote:
> > >> Hello,
> > >>
> > >>
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:04:52AM +0100, Johannes Pointner wrote:
> >> Hello,
> >>
> >> I have noticed that since we are using xf86-input-libinput all our
> >> touchs
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 of 15 for
>> maxTouchPoints.
>> Aft
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 of 15 for
> maxTouchPoints.
> After further looking into this I saw that xf86-input-libinput sets
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
