Use pointermove instead of mousemove to allow touch interactions to work

[nedredmond]

Just swaps out mousemove in favor of pointermove, which encapsulates mouse, touch, and pen events. Since PointerEvent inherits from MouseEvent, there is no other change needed for this to work. See the MDN page for PointerEvent.

The other bound event, click, already handles touch events, so nothing else is needed to make this plugin compatible with touch events.

Should fix #66 (as far as touchmove -- the other two are fixed by using pointer events to cover all interactions)

[Fuzzyma]

@nedredmond are there any mouse events you didnt cover?
Asking because if this:

the other two are fixed by using pointer events to cover all interactions

[nedredmond]

@nedredmond are there any mouse events you didnt cover?
Asking because if this:

the other two are fixed by using pointer events to cover all interactions

I meant those two "other two" (touchstart and touchend) are handled by the consumer, and it works if they use pointer events instead, as in drawArea.pointerdown((e) => drawing.draw()) and drawArea.pointerup((e) => drawing.draw("stop")) (not sure I'm getting the syntax right, on my phone -- but you get it) which cover mouse, touch, and stylus events.

I think the user that reported the issue was seeing that the draw between touch start and touch end didn't work. With pointermove, it will.

[Fuzzyma]

Ah OK. I see. Thanks :)