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
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
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
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
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
