On Fri, Oct 24, 2014 at 01:18:06PM -0500, Derek Foreman wrote:
> Currently libinput users just see choppy input if the kernel event queue
> overflows. This patch passes along an event so the caller can at least
> log it.
any reason you didn't just log it through libinput if that's all you want to
On Sun, Oct 26, 2014 at 01:10:43PM +0100, Stefanie Behme wrote:
> Am 21.10.2014 um 21:03 schrieb Carsten Haitzler (The Rasterman):
> >On Tue, 21 Oct 2014 20:21:26 +0200 Stefanie Behme
> >said:
> >
> >>Hi,
> >>
> >>on last ELCE in Duesseldorf I learned that the development of libinput
> >>was star
2014-10-26 10:45 GMT+02:00 Michael Johnson :
> Hi all,
>
> I'm using Arch linux 32 bit to develop a sample application on Wayland. My
> question is, if I've installed the Wayland and Weston packages using pacman,
> shouldn't the files (headers and libraries) used to run the client examples
> in th
On Sun, 26 Oct 2014 13:10:43 +0100 Stefanie Behme said:
> Am 21.10.2014 um 21:03 schrieb Carsten Haitzler (The Rasterman):
> > On Tue, 21 Oct 2014 20:21:26 +0200 Stefanie Behme
> > said:
> >
> >> Hi,
> >>
> >> on last ELCE in Duesseldorf I learned that the development of libinput
> >> was starte
Am 21.10.2014 um 21:03 schrieb Carsten Haitzler (The Rasterman):
On Tue, 21 Oct 2014 20:21:26 +0200 Stefanie Behme said:
Hi,
on last ELCE in Duesseldorf I learned that the development of libinput
was started to handle input devices in Wayland compositors. I had a look
in the API documentation
Hi all,
I'm using Arch linux 32 bit to develop a sample application on
Wayland. My question is, if I've installed the Wayland and Weston
packages using pacman, shouldn't the files (headers and libraries)
used to run the client examples in the Weston source
