On Tue, Jan 29, 2019 at 03:36:41PM +0200, Pekka Paalanen wrote:
> On Tue, 29 Jan 2019 16:57:34 +1000
> Peter Hutterer wrote:
>
> > The new API returns scroll wheels as fractions of 120.
> >
> > Signed-off-by: Peter Hutterer
> > ---
> > Turns out it's not the most complicated patch...
> >
> > T
Calling printf("%s", NULL) is undefined behaviour.
Signed-off-by: Simon Ser
---
src/connection.c | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/src/connection.c b/src/connection.c
index f965210..474c97b 100644
--- a/src/connection.c
+++ b/src/connection.c
@@ -1278,7 +127
On Tue, Jan 29, 2019 at 02:19:08PM +, Simon Ser wrote:
> On Tuesday, January 29, 2019 7:57 AM, Peter Hutterer
> wrote:
> > switch (source) {
> > case LIBINPUT_POINTER_AXIS_SOURCE_WHEEL:
> > +#if HAVE_LIBINPUT_AXIS_V120
> > + value = 10 * libinput_event_pointer_get_axis_value
On Tuesday, January 29, 2019 7:57 AM, Peter Hutterer
wrote:
> switch (source) {
> case LIBINPUT_POINTER_AXIS_SOURCE_WHEEL:
> +#if HAVE_LIBINPUT_AXIS_V120
> + value = 10 * libinput_event_pointer_get_axis_value_v120(
> +
On Tue, 20 Nov 2018 18:02:50 +1100
Christopher James Halse Rogers wrote:
> Many languages such as C++ or Rust have an unwinding error-reporting
> mechanism. Code in these languages can (and must!) wrap request handling
> callbacks in unwind guards to avoid undefined behaviour.
>
> As a consequen
On Tue, 29 Jan 2019 16:57:34 +1000
Peter Hutterer wrote:
> The new API returns scroll wheels as fractions of 120.
>
> Signed-off-by: Peter Hutterer
> ---
> Turns out it's not the most complicated patch...
>
> This is an RFC only because libinput hasn't been released yet, and it's
> waiting on
On Tue, 29 Jan 2019 16:02:16 +1100
Graeme Gill wrote:
> Pekka Paalanen wrote:
>
> >>> Yes, a compositor must implement all that, but this is now slipping to
> >>> the topic of calibration, which is very much off-scope for today. We
> >>> only want to consider how applications produce and provid
