Clients reading their surface position on screen

[Gerry Boland]

On 15/08/14 08:17, Christopher James Halse Rogers wrote:
> On Fri, Aug 15, 2014 at 5:14 PM, Gerry Boland
> <gerry.boland at canonical.com> wrote:
> > On 15/08/14 00:56, Christopher James Halse Rogers wrote:
> >>  On Fri, Aug 15, 2014 at 9:32 AM, Gerry Boland
> >>  <gerry.boland at canonical.com> wrote:
> >>  > On 14/08/14 00:31, Christopher James Halse Rogers wrote:
> >>  >>  Ok. I think we've explored all the relevant options
> >>  >>
> >>  >>  If I implemented
> >>  >>
> >>  >>  mir_debug_surface_coord_to_screen(MirSurface, int x, int y, int*
> >> outx,
> >>  >>  int* outy)
> >>  >>
> >>  >>  in libmirclient-debug and hooked it up to a --debug flag, who would
> >>  >>  object, and what would those objections be?
> >>  >>
> >>  >>
> >>  >
> >>  > And libmirclient-debug is shipped in a separate package which isn't
> >>  > installed on the device by default? Just thinking how this feature
> >> will
> >>  > not be accessible to all apps.
> >>
> >>  Correct. Also, Unity8 won't respond to these requests unless started
> >>  with --debug. Which we obviously won't do by default.
> >>
> >>  So, it's available to all apps when debugging is enabled, or no apps
> >>  when debugging is not enabled.
> >>
> >
> > Thomi, what do you think? Unity8 will need to be restarted with a flag
> > in order to enable this for AP. That ok?
> > -G
>
> I had a talk with Thomi on IRC this morning; rather than restart Unity8
> with this flag we can just have Unity8 started with this flag on the CI
> devices (and then modify the tests that restart Unity8).
>
> And by “we” I mean “I” ☺.
>
Perhaps AP could tell unity8 - go into debug mode - via dbus (hole poked in AppArmor required though)? Saves a restart of the process.