Pointer move with Touch backend should take into account when it is pressed
Bug #1266601 reported by
Leo Arias
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Autopilot |
Fix Released
|
High
|
Leo Arias | ||
| autopilot (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
| Vivid |
New
|
Undecided
|
Unassigned | ||
Bug Description
Currently, when we have a Pointer instance with a Touch backend, the move only updates the coordinates for the next press or click.
This doesn't work as expected for a sequence of statements press; move; release, because the move will do nothing and the release will be done on the same point.
We need a flag to tell the move if the pointer was pressed, and if it is true, the move should actually perform a finger move.
Related branches
lp:~elopio/autopilot/fix1266601-Pointer-pressed-move
- PS Jenkins bot: Needs Fixing (continuous-integration)
- Thomi Richards (community): Needs Information
-
Diff: 178 lines (+67/-23)3 files modifiedautopilot/input/__init__.py (+2/-0)
autopilot/input/_uinput.py (+4/-2)
autopilot/tests/unit/test_input.py (+61/-21)
lp:~canonical-platform-qa/autopilot/fix1266601-Pointer-pressed-move-2
- PS Jenkins bot: Approve (continuous-integration)
- Christopher Lee (community): Approve
- Richard Huddie (community): Approve
-
Diff: 588 lines (+235/-105)4 files modifiedautopilot/input/__init__.py (+7/-22)
autopilot/input/_uinput.py (+69/-29)
autopilot/tests/functional/test_input_stack.py (+6/-4)
autopilot/tests/unit/test_input.py (+153/-50)
| Changed in autopilot: | |
| status: | Confirmed → In Progress |
| assignee: | nobody → Leo Arias (elopio) |
Revision history for this message
| Christopher Lee (veebers) wrote | #1 |
Revision history for this message
| Leo Arias (elopio) wrote | #2 |
| Changed in autopilot: | |
| importance: | Undecided → High |
Revision history for this message
| PS Jenkins bot (ps-jenkins) wrote | #3 |
| Changed in autopilot: | |
| status: | In Progress → Fix Committed |
| Changed in autopilot: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
Leo, has there been any movement on this bug/branch? It seems that this would still be useful.