Re: [pointerevents] Stylus eraser: should it be a new pointerType instead of a button state?

> so what would happen if a stylus is either hovering or touching the 
digitizer, and then the eraser barrel button is pressed? does it need 
to pretend that the pen left (so firing off pointerout, pointerleave),
 and the new eraser pointer entered (pointerover, pointerenter)?

I see that pointerType="eraser" model will have to pretend pen 
leaving-and-entering, which will be terrible! Thanks for the catch.

> or are we talking about having two separate models for pens with 
eraser button and pens which can be flipped (which is getting very 
confusing, at least to me)?

It seems to me that adding a Boolean property <code>IsInverted</code> 
works (as in the Windows case Dave Fleck mentioned):
- If distinguishing between the two eraser states (flipped vs 
buttoned) is important, we can leave the current eraser button as is. 
"Inverted pen" and "eraser button" are conceptually different enough 
to cause any confusion, right? And this change will be backward 
compatible with <code>IsInverted</code> defaulting to 
<code>false</code>.
- Or if we find two separate eraser models confusing, we can _replace_
 the current eraser button with the <code>IsInverted</code> property.


-- 
GitHub Notification of comment by mustaqahmed
Please view or discuss this issue at 
https://github.com/w3c/pointerevents/issues/134#issuecomment-244193881
 using your GitHub account

Received on Thursday, 1 September 2016 19:58:16 UTC