Re: [PATCH libinput] test: add litest helper functions for creating uinput devices

2014-03-28 Thread Jonas Ådahl
On Fri, Mar 28, 2014 at 03:22:44PM +1000, Peter Hutterer wrote: > On Thu, Mar 27, 2014 at 05:10:34PM +0100, Jonas Ådahl wrote: > > On Thu, Mar 27, 2014 at 08:48:02AM +1000, Peter Hutterer wrote: > > > Both functions accept a series of event types/codes tuples, terminated by > > > -1. > > > For the

Re: [PATCH libinput] test: add litest helper functions for creating uinput devices

2014-03-27 Thread Peter Hutterer
On Thu, Mar 27, 2014 at 05:10:34PM +0100, Jonas Ådahl wrote: > On Thu, Mar 27, 2014 at 08:48:02AM +1000, Peter Hutterer wrote: > > Both functions accept a series of event types/codes tuples, terminated by > > -1. > > For the even type INPUT_PROP_MAX (an invalid type otherwise) the code is > > use

Re: [PATCH libinput] test: add litest helper functions for creating uinput devices

2014-03-27 Thread Jonas Ådahl
On Thu, Mar 27, 2014 at 08:48:02AM +1000, Peter Hutterer wrote: > Both functions accept a series of event types/codes tuples, terminated by -1. > For the even type INPUT_PROP_MAX (an invalid type otherwise) the code is used > as a property to enable. > > The _abs function als takes an array of abs

[PATCH libinput] test: add litest helper functions for creating uinput devices

2014-03-26 Thread Peter Hutterer
Both functions accept a series of event types/codes tuples, terminated by -1. For the even type INPUT_PROP_MAX (an invalid type otherwise) the code is used as a property to enable. The _abs function als takes an array of absinfo, with absinfo.value determining the axis to change. If none are given