On Mon, Feb 16, 2015 at 10:48:44PM -0500, Stephen Chandler Paul wrote:
> Having a motion event that's sent right after the original proximity event
> just
> to give the values of each axis is somewhat redundant. Since we already
> include
> the values of each axis with each type of event, we may
Having a motion event that's sent right after the original proximity event just
to give the values of each axis is somewhat redundant. Since we already include
the values of each axis with each type of event, we may as well use the
proximity event to give the client the starting values for each axi
