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

Re: Mouse Lock

From: Glenn Maynard <glenn@zewt.org>
Date: Fri, 24 Jun 2011 14:23:43 -0400
Message-ID: <BANLkTi=6sxhE9M8iSmYZNUnKOuhz40XMnQ@mail.gmail.com>
To: Aryeh Gregor <Simetrical+w3c@gmail.com>
Cc: Simon Pieters <simonp@opera.com>, "Tab Atkins Jr." <jackalmage@gmail.com>, Adam Barth <w3c@adambarth.com>, Vincent Scheib <scheib@google.com>, Brandon Andrews <warcraftthreeft@sbcglobal.net>, "Gregg Tavares (wrk)" <gman@google.com>, Charles Pritchard <chuck@jumis.com>, Kenneth Russell <kbr@google.com>, robert@ocallahan.org, public-webapps@w3.org
On Fri, Jun 24, 2011 at 1:58 PM, Aryeh Gregor <Simetrical+w3c@gmail.com>wrote:

> But this does highlight the fact that we probably want to support
> mouse-locking that doesn't hide the cursor also, for this kind of
> mouse-based scrolling.  In that case, though, the coordinates and
> mouse events should behave just like regular.  If the user presses the
> cursor up against the side of the screen and it visually stops moving,
> no mousemove events should be fired even if the user does keep moving
> the actual mouse.  The application would then want to check the
> cursor's location instead of listening for events.

"Walling the mouse cursor into a box" and "changing the mouse to a delta
movement device" are separate concepts.  They shouldn't be wedged
together--it may not even be possible to implement both at the same time, as
discussed earlier.

Glenn Maynard
Received on Friday, 24 June 2011 18:24:19 UTC

This archive was generated by hypermail 2.3.1 : Friday, 27 October 2017 07:26:32 UTC