[05:46] <fritsch> bschaefer: perfect
[10:12] <om26er> bug 1641901 says Hi!
[10:12] <ubot5`> bug 1641901 in MirAL "Need surface geometry for autopilot" [Undecided,New] https://launchpad.net/bugs/1641901
[10:26] <alan_g> om26er: mir_debug_surface_coords_to_screen() waves back
[10:31] <om26er> alan_g: hm, that looks like a bool[1], I presume it requires some parameters that we are actually trying to determine. [1] http://bazaar.launchpad.net/~mir-team/mir/development-branch/view/head:/src/client/mir_debug_api.cpp#L34
[10:33] <alan_g> https://bazaar.launchpad.net/~mir-team/mir/development-branch/view/head:/include/client/mir_toolkit/debug/surface.h#L48
[10:38] <alan_g> om26er: the bool tells you whether this extension has been enabled by the server.
[11:34] <alan_g> greyback: any likelyhood of miral reviews today?
[11:34] <greyback> alan_g: sure
[11:57] <om26er> alan_g: re your comment on the bug report. "Mir-0.25 provides a server-side API that allows this debug extension to be enabled dynamically. E.g. by Unity8"
[11:57] <om26er> Do you think it would make more sense to keep this feature one layer above unity8 ? think of the case of a Kiosk-like environment where unity8 is not the server. That way we can enable autopilot to work on more environments.
[12:00] <om26er> that brings me to question, will starting `unity8 --debug` enable the debug extensions ?
[12:01] <alan_g> om26er: *any* Mir server will respect the "debug" option which can be supplied at startup via commandline, environment variable or config file. The server-side API is available in Mir-0.25 & MirAL-0.5, but needs a mechanism for the server to call it
[12:02] <alan_g> In short, yes "unity8 --debug" will work
[12:03] <alan_g> I understand from greyback that there's a desire to do this dynamically (via dbus) for some test scenarios
[12:03] <alan_g> A kiosk implementation probably doesn't need dbus.
[12:12] <alan_g> greyback: thanks for the reviews. (ALL approved!?)
[12:12] <greyback> alan_g: you did good :)
[12:13] <greyback> alan_g: I only questioned if "debug extensions" should be plural
[12:13] <greyback> which is a nitpick of the highest order
[12:13] <alan_g> but a perfectly good one
[12:16] <alan_g> To me it sounds better (and future proof) with the "s", but multiple APIs could be "an extension" so I see your point
[12:21] <greyback> not something worth blocking on