Hey Daniel :),
On Tue, Nov 22, 2016 at 12:43 PM, Daniel Stone wrote:
> Hi Carlos,
>
> On 12 November 2015 at 12:31, Carlos Garnacho wrote:
>> The leave events in the respective device interfaces has been further
>> documented so those can convey the necessary info when input is being
>> redirect
Hi Carlos,
On 12 November 2015 at 12:31, Carlos Garnacho wrote:
> The leave events in the respective device interfaces has been further
> documented so those can convey the necessary info when input is being
> redirected out of their currently focused surface.
>
> Only wl_touch is missing somethi
On Monday, 16 November 2015, Bill Spitzak wrote:
>
> Exit events generated by the client's own actions are a huge pain, it
> forces clients to look ahead for the enter event to distinguish between the
> focus moving to another surface and losing it entirely. This should be
> fixed. A few ideas:
>
On Thu, Nov 12, 2015 at 4:31 AM, Carlos Garnacho wrote:
> The leave events in the respective device interfaces has been further
> documented so those can convey the necessary info when input is being
> redirected out of their currently focused surface.
>
> Only wl_touch is missing something seman
The leave events in the respective device interfaces has been further
documented so those can convey the necessary info when input is being
redirected out of their currently focused surface.
Only wl_touch is missing something semantically similar, a wl_touch.leave
event has been added so the touch
