On Tue, Mar 03, 2015 at 12:29:28PM -0500, Benjamin Tissoires wrote:
> On Mon, Mar 2, 2015 at 10:29 PM, Benjamin Tissoires
> wrote:
> > On Mon, Mar 2, 2015 at 7:59 PM, Peter Hutterer
> > wrote:
> >> If a tool is in proximity when we init, send a proximity event immediately.
> >>
> >> This is only
On Mon, Mar 2, 2015 at 10:29 PM, Benjamin Tissoires
wrote:
> On Mon, Mar 2, 2015 at 7:59 PM, Peter Hutterer
> wrote:
>> If a tool is in proximity when we init, send a proximity event immediately.
>>
>> This is only partially reliable due to the current kernel behavior:
>> * if the tool comes int
On Mon, Mar 2, 2015 at 7:59 PM, Peter Hutterer wrote:
> If a tool is in proximity when we init, send a proximity event immediately.
>
> This is only partially reliable due to the current kernel behavior:
> * if the tool comes into proximity when there is no evdev client, the device
> won't send
If a tool is in proximity when we init, send a proximity event immediately.
This is only partially reliable due to the current kernel behavior:
* if the tool comes into proximity when there is no evdev client, the device
won't send any events and must be lifted out-of-proximity first.
* if the t
