Re: [w3c/pointerlock] `movementX` and `movementY` for `pointermove` (and `pointerrawupdate`) should be the difference from the previous event for the same `pointerId` (Issue #104)

masayuki-nakano left a comment (w3c/pointerlock#104)

Well, honestly, I don't have concrete ideas how to use `movementX` and `movementY` of `pointermove` so that I'm not sure whether managing per `pointerId` is over action for the web API or expected by the API users of `pointermove`.

On the other hand, about `movementX` and `movementY` of `pointerrawupdate`, in my understanding, `pointerrawupdate` is useful for pen input handling and there is `.persistentDeviceId`. So, I guess that `pointerrawupdate` users may assume multiple pointer usages and it seems that `movementX` and `movementY` are useful to compute smooth curves at the path of moving a pen. Therefore, I think that should be managed per `pointerId`.

(In my understanding, `movementX` and `movementY` are also used without Pointer Lock. Therefore, it seems that managing per `pointerId` may be expected by the web developers.)

It's better to listen to the voice of web developers before considering the conclusion?

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3c/pointerlock/issues/104#issuecomment-3644632977
You are receiving this because you are subscribed to this thread.

Message ID: <w3c/pointerlock/issues/104/3644632977@github.com>