W3C home > Mailing lists > Public > public-webapps@w3.org > April to June 2011

Re: Mouse Lock

From: Gregg Tavares (wrk) <gman@google.com>
Date: Sun, 19 Jun 2011 12:39:04 -0700
Message-ID: <BANLkTino9tomtoPrCT4m0S3i=ub7P4FFJQ@mail.gmail.com>
To: Olli@pettay.fi
Cc: Vincent Scheib <scheib@google.com>, Brandon Andrews <warcraftthreeft@sbcglobal.net>, Glenn Maynard <glenn@zewt.org>, Charles Pritchard <chuck@jumis.com>, Kenneth Russell <kbr@google.com>, robert@ocallahan.org, public-webapps@w3.org
On Sun, Jun 19, 2011 at 5:10 AM, Olli Pettay <Olli.Pettay@helsinki.fi>wrote:

> On 06/17/2011 01:21 AM, Vincent Scheib wrote:
>
>> - 2 new methods on an element to enter and exit mouse lock. Two
>> callbacks on the entering call provide notification of success or failure.
>> - Mousemove event gains .deltaX .deltaY members, always valid, not just
>> during mouse lock.
>>
> I don't understand the need for .deltaX/Y.
>

I'm sure there are lots of other use cases but a typical use case for deltaX
and deltaY is camera movement in a first person game. You move the mouse to
the left to look left. The current mouseX, mouseY stop when mouse hits the
edge of the window/screen. deltaX, deltaY do not stop.


>
> More comments later.
>
>
> -Olli
>
Received on Sunday, 19 June 2011 19:39:31 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:45 GMT