Clients reading their surface position on screen

[Daniel d'Andrada]

On 13/08/14 10:12, Gerry Boland wrote:
> On 13/08/14 13:59, Daniel d'Andrada wrote:
>> I've yet another suggestion:
>>
>> unity8 provides a D-Bus API for autopilot to ask "hey, what's the
>> position/transformation of surface X?". Then AP would apply that
>> transformation to a surface local coordinate and send the resulting
>> global coordinate through evdev.
>>
>> advantages:
>>   - we don't hassle mir
>>   - AP still send its input events through evdev, which exercises the
>> whole input stack
>>
>> disadvantages:
>>   - more work to autopilot and unity8
>>
> This was option 1 in the original email, and disliked greatly by Thomi.
> It requires AP punching open appArmor rules between clients & unity8
> when running tests. DBus has much greater latency. Also would require
> notion of surface ID, which Mir folks also dislike.
>
> I left it out of further discussion as a result.
> -G
>
>

Ah, right. :)