On Sep 5, 2015 5:13 AM, "Peter Hutterer" wrote:
>
> On Fri, Sep 04, 2015 at 11:47:09PM +0530, Seedo Eldho Paul wrote:
> > xalloc terminates the program abruptly if the requested amount of
> > memory couldn't be allocated. To insure that the errors are handled
> > cleanly, use zalloc instead.
> >
>
On Fri, Sep 04, 2015 at 11:47:09PM +0530, Seedo Eldho Paul wrote:
> xalloc terminates the program abruptly if the requested amount of
> memory couldn't be allocated. To insure that the errors are handled
> cleanly, use zalloc instead.
>
> Signed-off-by: Seedo Eldho Paul
> ---
> tests/internal-sc
xalloc terminates the program abruptly if the requested amount of
memory couldn't be allocated. To insure that the errors are handled
cleanly, use zalloc instead.
Signed-off-by: Seedo Eldho Paul
---
tests/internal-screenshot-test.c | 11 ++-
1 file changed, 6 insertions(+), 5 deletions(-
Signed-off-by: Andreas Pokorny
---
test/litest.c | 8 +---
1 file changed, 5 insertions(+), 3 deletions(-)
diff --git a/test/litest.c b/test/litest.c
index 29e764b..38e313e 100644
--- a/test/litest.c
+++ b/test/litest.c
@@ -932,13 +932,15 @@ merge_events(const int *orig, const int *override
Hi,
On 04-09-15 09:09, Peter Hutterer wrote:
The following sequence currently generates a right-button event:
finger 1 down
finger 2 down
finger 1 up
finger 2 held down
This is easily triggered with short scroll events. There are two issues here:
first is that th
The following sequence currently generates a right-button event:
finger 1 down
finger 2 down
finger 1 up
finger 2 held down
This is easily triggered with short scroll events. There are two issues here:
first is that the tapping code elsewhere treats any tap with a s
