Re: [w3c/pointerlock] Pointer Clip (#27)

Just noting here that we have a strong use case for this for RTS games where the mouse needs to be visible and push the sides of the screen.  Drawing the mouse cursor via CSS each time the offsets update introduces noticeable studder.  Also needed is to be able to change the mouse cursor that is pointer locked (so the default is not displayed).  Something like the way NaCL did/does it was great.  And it of course should be a hardware cursor.

Another enhancement to this, is to present absolute events, not just relative ones.  Why?

For the remote desktop scenario, you cannot rely on a server side mouse as its way too behind/laggy.  So you must use a client mouse pointer and hide the server pointer.  But when relying on relative coordination to forward the mouse position to the server side, any small misalignment, or if the sever side OS has mouse acceleration applied will throw off the cursor once the input gets injected into the server side OS.  The only reliable solution is to send absolute coordinates.

-- 
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/27#issuecomment-339018906