Re: [PATCH libinput 0/5] tablet: change to an axis-specific API

2015-12-14 Thread Lyude
+1 for this idea, this looks a lot cleaner to work with then what we had before. I've gone through all the patches, and since most of it is refactoring the only issue I can see is the typo in #4. Consider it Reviewed-by: Lyude On Mon, 2015-12-14 at 12:00 +1000, Peter Hutterer wrote: > This patch

Re: [PATCH libinput 0/5] tablet: change to an axis-specific API

2015-12-14 Thread Hans de Goede
Hi, On 14-12-15 03:00, Peter Hutterer wrote: This patchset changes the Tablet API from an API where we have a few functions that take an axis type into one where we have an API that is specific to each axis type. The one-size-fits-all approach turned out to be too inflexible to be useful and f

[PATCH libinput 0/5] tablet: change to an axis-specific API

2015-12-13 Thread Peter Hutterer
This patchset changes the Tablet API from an API where we have a few functions that take an axis type into one where we have an API that is specific to each axis type. The one-size-fits-all approach turned out to be too inflexible to be useful and forced a couple of special API behaviours, e.g. g