On Sun, Mar 27, 2011 at 12:51:32PM -0700, Ping Cheng wrote:
> On Sat, Mar 26, 2011 at 6:26 PM, Chris Bagwell wrote:
>
> > On Thu, Mar 24, 2011 at 5:35 PM, Ping Cheng wrote:
> > > Change oldHwProx to oldCursorHwProx to better refect its use.
> > >
> > > Protocol 5 distance starts from the MaxCurs
On Sat, Mar 26, 2011 at 6:26 PM, Chris Bagwell wrote:
> On Thu, Mar 24, 2011 at 5:35 PM, Ping Cheng wrote:
> > Change oldHwProx to oldCursorHwProx to better refect its use.
> >
> > Protocol 5 distance starts from the MaxCursorDist (256) when
> > getting in the prox while protocol 4 distance is 0
On Thu, Mar 24, 2011 at 5:35 PM, Ping Cheng wrote:
> Change oldHwProx to oldCursorHwProx to better refect its use.
>
> Protocol 5 distance starts from the MaxCursorDist (256) when
> getting in the prox while protocol 4 distance is 0 when
> getting in the prox.
>
> oldCursorHwProx keeps the hardwar
I found two typoes in the commit comment. I'll update them if changes are
needed in the code. Otherwise, please amend them before merging.
Thanks,
Ping
On Fri, Mar 25, 2011 at 6:35 AM, Ping Cheng wrote:
> Change oldHwProx to oldCursorHwProx to better refect its use.
>
reflect
> Protocol 5 d
Change oldHwProx to oldCursorHwProx to better refect its use.
Protocol 5 distance starts from the MaxCursorDist (256) when
getting in the prox while protocol 4 distance is 0 when
getting in the prox.
oldCursorHwProx keeps the hardware in/out prox state so we can
we set the MaxCursorDist for the n
