Overlapping same-gesture areas with different start touches broken
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OIF-qml |
Fix Released
|
High
|
Chase Douglas | ||
utouch-qml (Ubuntu) |
Fix Released
|
High
|
Chase Douglas |
Bug Description
From an email of a Darren West:
I am trying to setup two or more touch areas occupying the same space, one with a 3 finger and one with a 4 finger subscription, however, whichever is declared last will then block the previous topAreas signals and the subscription looks like it gets confused with how many fingers are required. So:
UTouchTapArea {
subscription {
}
}
UTouchTapArea {
touches.start : 4
}
}
Will log '4 finger tap' regardless of whether it was a 3 or 4 finger tap!
Related branches
- Stephen M. Webb (community): Approve
-
Diff: 13 lines (+3/-0)1 file modifiedsrc/geissingleton.cpp (+3/-0)
Changed in utouch-qml: | |
status: | In Progress → Fix Committed |
affects: | ubuntu → utouch-qml (Ubuntu) |
Changed in utouch-qml (Ubuntu): | |
assignee: | nobody → Chase Douglas (chasedouglas) |
importance: | Undecided → High |
status: | New → In Progress |
Changed in utouch-qml: | |
status: | Fix Committed → Fix Released |
Changed in utouch-qml (Ubuntu): | |
status: | In Progress → Fix Committed |
uTouch-qml currently does not check if the number of touches in the begin gesture matches the number of touches subscribed. This isn't an issue if same-gesture areas don't overlap, but when they do it can cause the wrong area to receive the events.