{"action":"created","issue":{"url":"https://api.github.com/repos/w3c/pointerevents/issues/152","repository_url":"https://api.github.com/repos/w3c/pointerevents","labels_url":"https://api.github.com/repos/w3c/pointerevents/issues/152/labels{/name}","comments_url":"https://api.github.com/repos/w3c/pointerevents/issues/152/comments","events_url":"https://api.github.com/repos/w3c/pointerevents/issues/152/events","html_url":"https://github.com/w3c/pointerevents/issues/152","id":186327763,"number":152,"title":"pointerType: 'dial'","user":{"login":"appsforartists","id":926648,"avatar_url":"https://avatars.githubusercontent.com/u/926648?v=3","gravatar_id":"","url":"https://api.github.com/users/appsforartists","html_url":"https://github.com/appsforartists","followers_url":"https://api.github.com/users/appsforartists/followers","following_url":"https://api.github.com/users/appsforartists/following{/other_user}","gists_url":"https://api.github.com/users/appsforartists/gists{/gist_id}","starred_url":"https://api.github.com/users/appsforartists/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/appsforartists/subscriptions","organizations_url":"https://api.github.com/users/appsforartists/orgs","repos_url":"https://api.github.com/users/appsforartists/repos","events_url":"https://api.github.com/users/appsforartists/events{/privacy}","received_events_url":"https://api.github.com/users/appsforartists/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":9,"created_at":"2016-10-31T16:19:04Z","updated_at":"2016-11-04T21:35:22Z","closed_at":null,"body":"@jacobrossi, do you know if there are plans for the [Windows Wheel](https://msdn.microsoft.com/en-us/windows/uwp/input-and-devices/windows-wheel-interactions) devices to emit pointer events?\r\n\r\nThis question may be a bit premature, since the [three presently-defined `pointerTypes`](https://w3c.github.io/pointerevents/#dom-pointerevent-pointertype) have all been commercially successful for quite some time; whereas, the Surface Dial is the first dial pointer I'm aware of to be broadly marketed.  Still, since it's one of the few fundamentally-new pointer types, specifying its behavior may be worthwhile."},"comment":{"url":"https://api.github.com/repos/w3c/pointerevents/issues/comments/258553526","html_url":"https://github.com/w3c/pointerevents/issues/152#issuecomment-258553526","issue_url":"https://api.github.com/repos/w3c/pointerevents/issues/152","id":258553526,"user":{"login":"mustaqahmed","id":8505377,"avatar_url":"https://avatars.githubusercontent.com/u/8505377?v=3","gravatar_id":"","url":"https://api.github.com/users/mustaqahmed","html_url":"https://github.com/mustaqahmed","followers_url":"https://api.github.com/users/mustaqahmed/followers","following_url":"https://api.github.com/users/mustaqahmed/following{/other_user}","gists_url":"https://api.github.com/users/mustaqahmed/gists{/gist_id}","starred_url":"https://api.github.com/users/mustaqahmed/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/mustaqahmed/subscriptions","organizations_url":"https://api.github.com/users/mustaqahmed/orgs","repos_url":"https://api.github.com/users/mustaqahmed/repos","events_url":"https://api.github.com/users/mustaqahmed/events{/privacy}","received_events_url":"https://api.github.com/users/mustaqahmed/received_events","type":"User","site_admin":false},"created_at":"2016-11-04T21:35:22Z","updated_at":"2016-11-04T21:35:22Z","body":"PointerEvents can be tweaked to represent a \"dial\" (Windows Wheel) for sure. But before we commit to changes in this direction, we should discuss the pros & cons of other comparable alternatives. Here are my thoughts on one such alternative: WheelEvents could also be tweaked to represent the device too---is it really bad compared to PointerEvents?\r\n\r\nBoth PointerEvent and WheelEvent (each of them is a direct subclasses of MouseEvent) seem to have some unique winning points. I looked at three properties of a \"dial\", as follows. I found WheelEvents to be a better choice for two of them, YMMV.\r\n\r\n#### Dial rotation\r\nDial rotation comes first because it is the most prominent aspect of the new hardware. The dial is symmetric around its axis, so the exact _physical_ angle of the dial position seems immaterial to users, e.g. there is no left/right/up/down position. This is like a mouse-wheel, and unlike stylus devices (possibly with a \"calligraphic\" tip) for which PointerEvent.twist was added.\r\n\r\nThe [website](https://msdn.microsoft.com/en-us/windows/uwp/input-and-devices/windows-wheel-interactions) shows some nice widgets to mark dial position but the physical dial has no mark, to allow defining the \"position\" arbitrarily through software (which is a great thing IMO). Even if a software widget exactly simulates a physical marker position on the dial, the connection between the widget and the device breaks completely when the device goes off-screen. Consider this experiment: mark the dial (with a marker) at the widget-marked rotation angle, detach the device from the screen, bring it back at a different angle.\r\n\r\nClearly an absolute rotation angle (\"twist\") from the device would make no sense to the software. Only the rotation offset matters here. This is like WheelEvent.deltaZ as @shepazu mentioned above, and unlike PointerEvent.twist.\r\n\r\nSo dial rotation is more like turning a mouse wheel than twisting a pen, both physically & for the software interface.\r\n\r\n#### Device diameter\r\nWheelEvent doesn't have anything to offer here. PointerEvent wins, with width & height.\r\n\r\n#### Pointer location\r\nThe use-cases shown in Microsoft website seem to suggest that the location of the dial has only a weak association to the content below it. If a dial is off the screen, it's location is irrelevant, unlike any other pointing device. When the dial is about to touch the screen, it doesn't seem to affect the content below it but instead \"pops up\" a new UI widget, and then controls the part of the widget _around_ it. \"Center of of the Widget upon contact\" seems to be the only use of its location. Does it have any use case as a _pointing device_? I didn't find any.\r\n\r\nA mouse wheel is not used as a pointing tool (even though it \"resides\" on a pointing device). We don't move the mouse when turning the wheel---either for the physical awkwardness of simultaneous movements, or to avoid scrolling wrong things accidentally. Dial seems exactly like this: meant to be used by our \"non-dominant\" hand which is not an expert for precise movement, at least for me.\r\n\r\nThoughts?"}}
{"actor":{"display_login":"mustaqahmed"}}