Re: Clients reading their surface position on screen

2014-08-14 Thread Alan Griffiths
On 14/08/14 00:31, Christopher James Halse Rogers wrote: > > > 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? Returning a bool (or an enum?) t

Re: Clients reading their surface position on screen

2014-08-14 Thread Daniel van Vugt
I think a MirBool is enough. Although if anyone does implement the Qt function later then that one doesn't have such luxury. You would have to return some invalid Point for Qt. On 14/08/14 16:25, Alan Griffiths wrote: On 14/08/14 00:31, Christopher James Halse Rogers wrote: mir_debug_surfa

Re: Clients reading their surface position on screen

2014-08-14 Thread Christopher James Halse Rogers
On Thu, Aug 14, 2014 at 6:28 PM, Daniel van Vugt wrote: I think a MirBool is enough. Although if anyone does implement the Qt function later then that one doesn't have such luxury. You would have to return some invalid Point for Qt. Which is one reason why we absolutely should not implement t

Re: Clients reading their surface position on screen

2014-08-14 Thread Gerry Boland
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 > ob

Re: Clients reading their surface position on screen

2014-08-14 Thread Christopher James Halse Rogers
On Fri, Aug 15, 2014 at 9:32 AM, Gerry Boland 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 an