Merge lp://qastaging/~bregma/geis/lp-742555 into lp://qastaging/geis
Proposed by
Stephen M. Webb
Status: | Merged |
---|---|
Merged at revision: | 129 |
Proposed branch: | lp://qastaging/~bregma/geis/lp-742555 |
Merge into: | lp://qastaging/geis |
Diff against target: |
499 lines (+229/-56) 9 files modified
ChangeLog (+21/-0) include/geis/geis.h (+10/-0) libutouch-geis/backend/xcb/geis_xcb_backend.c (+10/-7) libutouch-geis/backend/xcb/grail_gestures.c (+102/-49) libutouch-geis/geis_v1.c (+5/-0) testsuite/geis1/Makefile.am (+1/-0) testsuite/geis1/check_geis1_api.c (+2/-0) testsuite/geis1/check_gesture_types.c (+77/-0) testsuite/geistest/geistest.c (+1/-0) |
To merge this branch: | bzr merge lp://qastaging/~bregma/geis/lp-742555 |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Chase Douglas (community) | Approve | ||
Review via email:
|
Description of the change
Adds through support for TOUCH gesture types for direct touch begin/end handling.
To post a comment you must log in.
I'd prefer to move to C99 and use dynamic array sizes than use alloca, just cause it seems more conventional.
The s_grail_class_map array has a bunch of changes to unaffected gesture types. It appears there's a comma added near the end of each line. I think the comma is superfluous and should be removed so there's no change.
grail_mask_clear could just use memset, which would make the code more readable.
Why does grail_mask_setbit only concern itself with the lower 5 bits of each uint32_t?
Although grail exposes velocity attributes for touch gestures, I don't want to expose the attributes through GEIS. I propose masking them out.
Looks good otherwise!