- From: Doug Schepers via GitHub <sysbot+gh@w3.org>
- Date: Mon, 31 Oct 2016 23:04:21 +0000
- To: public-pointer-events@w3.org
I agree that it may be useful for us to define a set of events related to a dial input, and adding a "dial" `pointerType` seems reasonable to me. Most of the specific functions are already defined using pre-existing events, though, and we should only define those things that are unique to the dial, or define a dial's characteristics in existing terms. Effectively, it's a mouse with rotation, much like a mouse with a mousewheel. - `x`, `y`: this would be the centerpoint of the dial. - size/radius/contact geometry would be available the same way it is with normal pointer events: `event.target.style.width` and `event.target.style.height`. - rotation should be defined as `deltaX`, `deltaY`, or `deltaZ` (depending on the axis mode), as defined in [UI Events](https://www.w3.org/TR/uievents/#events-wheelevents). - orientation is a possible property we could look at, though I don't think it's distinguishable from the rotation. - `zoom` (and `pan`) is something we've long had in SVG documents, and I think this is a property of the element or document more than an event; to the extent that it's expressed in events, I think it corresponds to `deltaZ`. - `press and hold` seems like it could be expressed as a `longkeypress` (though I don't see that in UI Events anymore) Can you think of any specific aspect of a dial that can't be expressed in a predefined way? Notably, you don't have to have a physical dial for these types of event properties to be used; in a AR/VR environment, it could be mapped to some specific gestures (e.g. extending the fingers and twisting the hand). -- GitHub Notification of comment by shepazu Please view or discuss this issue at https://github.com/w3c/pointerevents/issues/152#issuecomment-257445939 using your GitHub account
Received on Monday, 31 October 2016 23:04:27 UTC