- From: Nadav Sinai <notifications@github.com>
- Date: Thu, 12 Mar 2020 09:02:35 -0700
- To: w3c/pointerlock <pointerlock@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Thursday, 12 March 2020 16:02:48 UTC
Hi, Here at Philips we develop a medical imaging application that uses requestPointerLock extensively to allow for complex Mouse+keyboard operations on canvas. Specifically, the user may perform really long drags (for example for zooming) , which without the pointerlock would exit the canvas. We have a problem when the operation needs to be communicated via the pointer as well as the change in the image, for example in tools like ‘magnify glass’ tool - When the user releases the mouse, the cursor goes back to its initial location, and the user may have a long way to move the mouse to the new position of the magnify glass I know this has been discussed a little in #41, but the scenario is different. we suggest adding two optional arguments to exitPointerLock: a dx and dy to set the pointer to a new position just before making the pointer visible. ```` document.exitPointerLock(dx, dy); ```` -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3c/pointerlock/issues/61
Received on Thursday, 12 March 2020 16:02:48 UTC