W3C home > Mailing lists > Public > public-pointer-events@w3.org > April to June 2017

Re: [pointerevents] Should the spec defines how to handle when the pen's left button and the pen tip both are pressed?

From: dfleck via GitHub <sysbot+gh@w3.org>
Date: Thu, 11 May 2017 21:48:32 +0000
To: public-pointer-events@w3.org
Message-ID: <issue_comment.created-300926464-1494539311-sysbot+gh@w3.org>
Here's some background on how the side switches work:
The buttons are configurable by the user. By default the tip is left click, and the side switches are right click and left double click.
There are two situations regarding cording (pressing more than one) settable by the user:
1) "TabletPC" bahaviour (click and tap). In this case the side switches don't activate until the tip is clicked (so side switches are always combined with the tip). So to do a right click, you press the side switch then click with the tip and a right click is sent - not a left. This can make targetting easier since the action occurs on tip down (a downward motion) instead of pressing the side switch (a sideways motion) but it does require two actions and precludes cording.
2) True cording. An example here is setting a side switch to do a keyboard modifier, such as option. In this case the tip does a left click, but a side switch plus tip does an option click. This is useful in Photoshop where the option key inverts the action (draw becomes erase, dodge becomes burn)

Since a lot of the events thrown by the driver at a low level, the buttons will act as defined in the settings before PE can do anything (if a button is set to right click, a right click event will be sent by the driver).

My opinion:
If the user sets the side switch to "barrel button", the side switch and tip switch should be treated independently and the state of both buttons should be reported. Otherwise the driver will perfomr the actions specified by the settings.

-- 
GitHub Notification of comment by dfleck
Please view or discuss this issue at https://github.com/w3c/pointerevents/issues/207#issuecomment-300926464 using your GitHub account
Received on Thursday, 11 May 2017 21:48:39 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 11 May 2017 21:48:39 UTC