Merge lp:~mir-team/qtmir/fix-key-auto-repeat into lp:qtmir
Proposed by
Robert Carr
Status: | Merged | ||||
---|---|---|---|---|---|
Approved by: | Daniel d'Andrada | ||||
Approved revision: | 256 | ||||
Merged at revision: | 270 | ||||
Proposed branch: | lp:~mir-team/qtmir/fix-key-auto-repeat | ||||
Merge into: | lp:qtmir | ||||
Diff against target: |
47 lines (+8/-5) 2 files modified
src/modules/Unity/Application/mirsurfaceitem.cpp (+4/-3) src/platforms/mirserver/qteventfeeder.cpp (+4/-2) |
||||
To merge this branch: | bzr merge lp:~mir-team/qtmir/fix-key-auto-repeat | ||||
Related bugs: |
|
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Daniel d'Andrada (community) | Approve | ||
PS Jenkins bot (community) | continuous-integration | Approve | |
Review via email: mp+235873@code.launchpad.net |
Commit message
Pass key auto-repeat flag through QtEventFeeder.
This ensures that clients of a qtmir server will receive a value for MirKeyEvent.
Description of the change
Fix key auto repeat...note though we lose the actual count of repeat_count from the original mir event, and instead just end up using it as a boolean "is this an auto-repeat event". This works fine for Qt clients as they only deal with isAutoRep, but supposedly some mir clients could want to utilize the actual repeat_count (e.g. accelerating repeat...? I'm not really confident on the use case actually).
To post a comment you must log in.
PASSED: Continuous integration, rev:256 jenkins. qa.ubuntu. com/job/ qtmir-ci/ 88/ jenkins. qa.ubuntu. com/job/ qtmir-utopic- amd64-ci/ 88 jenkins. qa.ubuntu. com/job/ qtmir-utopic- armhf-ci/ 88 jenkins. qa.ubuntu. com/job/ qtmir-utopic- armhf-ci/ 88/artifact/ work/output/ *zip*/output. zip
http://
Executed test runs:
SUCCESS: http://
SUCCESS: http://
deb: http://
Click here to trigger a rebuild: s-jenkins. ubuntu- ci:8080/ job/qtmir- ci/88/rebuild
http://