Merge lp://qastaging/~andreas-pokorny/mir/fix-1531517-0.18 into lp://qastaging/mir
Proposed by
Andreas Pokorny
| Status: | Superseded | ||||
|---|---|---|---|---|---|
| Proposed branch: | lp://qastaging/~andreas-pokorny/mir/fix-1531517-0.18 | ||||
| Merge into: | lp://qastaging/mir | ||||
| Diff against target: |
560 lines (+459/-3) (has conflicts) 4 files modified
src/client/symbols.map (+13/-0) src/server/input/android/input_sender.cpp (+184/-0) src/server/input/android/input_sender.h (+17/-3) tests/unit-tests/input/android/test_android_input_sender.cpp (+245/-0) Text conflict in src/client/symbols.map Text conflict in src/server/input/android/input_sender.cpp Text conflict in src/server/input/android/input_sender.h Text conflict in tests/unit-tests/input/android/test_android_input_sender.cpp |
||||
| To merge this branch: | bzr merge lp://qastaging/~andreas-pokorny/mir/fix-1531517-0.18 | ||||
| Related bugs: |
|
| Reviewer | Review Type | Date Requested | Status |
|---|---|---|---|
| Mir development team | Pending | ||
|
Review via email:
|
|||
This proposal has been superseded by a proposal from 2016-01-13.
Commit message
Never encode more than one action per event
Android InputTransport has only one action parameter per event. Within that the contact that caused the action is also encoded. So until we replace or extend the input transport protocol, we have to split up MirEvents, to not lose touch up/down changes.
Additionally in this version of the fix. also a recent lp:mir cleanup that affected the tool type encoding of pointer events.
Description of the change
Similar to the change in lp:mir - but this fix also pulls in some clenaups in pointer event sending.
To post a comment you must log in.
Preview Diff
[H/L] Next/Prev Comment, [J/K] Next/Prev File, [N/P] Next/Prev Hunk
