Merge lp:~alan-griffiths/mir/request-with-authority into lp:mir
| Status: | Merged |
|---|---|
| Approved by: | Alan Griffiths on 2017-03-28 |
| Approved revision: | 4111 |
| Merged at revision: | 4122 |
| Proposed branch: | lp:~alan-griffiths/mir/request-with-authority |
| Merge into: | lp:mir |
| Diff against target: |
530 lines (+111/-157) 12 files modified
src/client/mir_surface.cpp (+16/-22) src/client/mir_surface.h (+1/-1) src/client/rpc/mir_display_server.cpp (+2/-10) src/client/rpc/mir_display_server.h (+2/-6) src/include/common/mir/protobuf/display_server.h (+2/-6) src/protobuf/mir_protobuf.proto (+7/-5) src/protobuf/symbols.map (+21/-20) src/server/frontend/protobuf_message_processor.cpp (+2/-6) src/server/frontend/session_mediator.cpp (+16/-25) src/server/frontend/session_mediator.h (+2/-6) tests/include/mir/test/doubles/stub_display_server.h (+36/-48) tests/unit-tests/frontend/test_session_mediator.cpp (+4/-2) |
| To merge this branch: | bzr merge lp:~alan-griffiths/mir/request-with-authority |
| Related bugs: |
| Reviewer | Review Type | Date Requested | Status |
|---|---|---|---|
| Andreas Pokorny (community) | 2017-03-23 | Approve on 2017-03-27 | |
| Mir CI Bot | continuous-integration | Approve on 2017-03-24 | |
|
Review via email:
|
|||
Commit Message
Refactor RPC to provide a more generic approach to window management requests that need authorization.
Description of the Change
Refactor RPC to provide a more generic approach to window management requests that need authorization.
My intention is to support new APIs using this RPC. Vis:
void mir_window_
void mir_window_
- 4109. By Alan Griffiths on 2017-03-23
-
DRY
- 4110. By Alan Griffiths on 2017-03-23
-
Pass enum by value
| Mir CI Bot (mir-ci-bot) wrote : | # |
PASSED: Continuous integration, rev:4110
https:/
Executed test runs:
SUCCESS: https:/
SUCCESS: https:/
SUCCESS: https:/
SUCCESS: https:/
SUCCESS: https:/
SUCCESS: https:/
deb: https:/
SUCCESS: https:/
deb: https:/
SUCCESS: https:/
deb: https:/
SUCCESS: https:/
deb: https:/
SUCCESS: https:/
deb: https:/
SUCCESS: https:/
deb: https:/
Click here to trigger a rebuild:
https:/
- 4111. By Alan Griffiths on 2017-03-24
-
merge :parent
| Mir CI Bot (mir-ci-bot) wrote : | # |
FAILED: Continuous integration, rev:4111
https:/
Executed test runs:
FAILURE: https:/
SUCCESS: https:/
SUCCESS: https:/
SUCCESS: https:/
SUCCESS: https:/
SUCCESS: https:/
deb: https:/
SUCCESS: https:/
deb: https:/
SUCCESS: https:/
deb: https:/
FAILURE: https:/
deb: https:/
SUCCESS: https:/
deb: https:/
SUCCESS: https:/
deb: https:/
Click here to trigger a rebuild:
https:/
| Mir CI Bot (mir-ci-bot) wrote : | # |
PASSED: Continuous integration, rev:4111
https:/
Executed test runs:
SUCCESS: https:/
SUCCESS: https:/
SUCCESS: https:/
SUCCESS: https:/
SUCCESS: https:/
SUCCESS: https:/
deb: https:/
SUCCESS: https:/
deb: https:/
SUCCESS: https:/
deb: https:/
SUCCESS: https:/
deb: https:/
SUCCESS: https:/
deb: https:/
SUCCESS: https:/
deb: https:/
Click here to trigger a rebuild:
https:/
| Andreas Pokorny (andreas-pokorny) wrote : | # |
I assume you plan to track MirCookie -> down-move-up gestures in mirserver - so stating the MirCookie is sufficient to identify the specific touch contact on the touchscreen or the specific pointing device, that when successfully matched will be tracked for motion?
lgtm otherwise
| Alan Griffiths (alan-griffiths) wrote : | # |
> I assume you plan to track MirCookie -> down-move-up gestures in mirserver -
> so stating the MirCookie is sufficient to identify the specific touch contact
> on the touchscreen or the specific pointing device, that when successfully
> matched will be tracked for motion?
Agreed, the window management policy needs the event to correctly interpret the request.
I didn't fancy introducing a transport mechanism to forward input events from the client to the server. Tracking the latest event (like the existing tracking of its timestamp) on the server seems far simpler.
| Andreas Pokorny (andreas-pokorny) wrote : | # |
> > I assume you plan to track MirCookie -> down-move-up gestures in mirserver -
> > so stating the MirCookie is sufficient to identify the specific touch
> contact
> > on the touchscreen or the specific pointing device, that when successfully
> > matched will be tracked for motion?
>
> Agreed, the window management policy needs the event to correctly interpret
> the request.
>
> I didn't fancy introducing a transport mechanism to forward input events from
> the client to the server. Tracking the latest event (like the existing
> tracking of its timestamp) on the server seems far simpler.
yes...

PASSED: Continuous integration, rev:4108 /mir-jenkins. ubuntu. com/job/ mir-ci/ 3224/ /mir-jenkins. ubuntu. com/job/ build-mir/ 4339 /mir-jenkins. ubuntu. com/job/ build-0- fetch/4426 /mir-jenkins. ubuntu. com/job/ build-1- sourcepkg/ release= vivid+overlay/ 4416 /mir-jenkins. ubuntu. com/job/ build-1- sourcepkg/ release= xenial+ overlay/ 4416 /mir-jenkins. ubuntu. com/job/ build-1- sourcepkg/ release= zesty/4416 /mir-jenkins. ubuntu. com/job/ build-2- binpkg- mir/arch= amd64,compiler= clang,platform= mesa,release= zesty/4371 /mir-jenkins. ubuntu. com/job/ build-2- binpkg- mir/arch= amd64,compiler= clang,platform= mesa,release= zesty/4371/ artifact/ output/ *zip*/output. zip /mir-jenkins. ubuntu. com/job/ build-2- binpkg- mir/arch= amd64,compiler= gcc,platform= mesa,release= xenial+ overlay/ 4371 /mir-jenkins. ubuntu. com/job/ build-2- binpkg- mir/arch= amd64,compiler= gcc,platform= mesa,release= xenial+ overlay/ 4371/artifact/ output/ *zip*/output. zip /mir-jenkins. ubuntu. com/job/ build-2- binpkg- mir/arch= amd64,compiler= gcc,platform= mesa,release= zesty/4371 /mir-jenkins. ubuntu. com/job/ build-2- binpkg- mir/arch= amd64,compiler= gcc,platform= mesa,release= zesty/4371/ artifact/ output/ *zip*/output. zip /mir-jenkins. ubuntu. com/job/ build-2- binpkg- mir/arch= cross-armhf, compiler= gcc,platform= android, release= vivid+overlay/ 4371 /mir-jenkins. ubuntu. com/job/ build-2- binpkg- mir/arch= cross-armhf, compiler= gcc,platform= android, release= vivid+overlay/ 4371/artifact/ output/ *zip*/output. zip /mir-jenkins. ubuntu. com/job/ build-2- binpkg- mir/arch= i386,compiler= gcc,platform= android, release= vivid+overlay/ 4371 /mir-jenkins. ubuntu. com/job/ build-2- binpkg- mir/arch= i386,compiler= gcc,platform= android, release= vivid+overlay/ 4371/artifact/ output/ *zip*/output. zip /mir-jenkins. ubuntu. com/job/ build-2- binpkg- mir/arch= i386,compiler= gcc,platform= mesa,release= xenial+ overlay/ 4371 /mir-jenkins. ubuntu. com/job/ build-2- binpkg- mir/arch= i386,compiler= gcc,platform= mesa,release= xenial+ overlay/ 4371/artifact/ output/ *zip*/output. zip
https:/
Executed test runs:
SUCCESS: https:/
SUCCESS: https:/
SUCCESS: https:/
SUCCESS: https:/
SUCCESS: https:/
SUCCESS: https:/
deb: https:/
SUCCESS: https:/
deb: https:/
SUCCESS: https:/
deb: https:/
SUCCESS: https:/
deb: https:/
SUCCESS: https:/
deb: https:/
SUCCESS: https:/
deb: https:/
Click here to trigger a rebuild: /mir-jenkins. ubuntu. com/job/ mir-ci/ 3224/rebuild
https:/