RE: [pointerevents] pointerType: 'dial'

The dial was designed to be a companion input device, not necessarily the only input device available. 
That being said, since the dial would have a location on the screen when the device is placed on the screen, it could be used for something like selection even if that wasn't the primary scenario for the device. I guess we would think of it similarly to a basic pen since it has direct screen contact.

-----Original Message-----
From: Ted Dinklocker [mailto:Ted.Dinklocker@microsoft.com] 
Sent: Tuesday, November 8, 2016 9:29 AM
To: Patrick H.Lauke via GitHub <sysbot+gh@w3.org>; public-pointer-events@w3.org
Subject: RE: [pointerevents] pointerType: 'dial'

I am checking with the dial team to see what their intentions are - I need to understand more about what the dial can do versus what the dial should do.

-----Original Message-----
From: Patrick H.Lauke via GitHub [mailto:sysbot+gh@w3.org] 
Sent: Tuesday, November 8, 2016 2:09 AM
To: public-pointer-events@w3.org
Subject: Re: [pointerevents] pointerType: 'dial'

> the dial is inherently not supposed to be used as a standalone 
single-pointer.

I can't locate the video just now, but I have seen the demo of using 
the dial when editing music notation where the dial itself is used as 
an actual pointer to click/select part of the music sheet to highlight
 it for editing. So I don't think that statement is necessarily true.

@teddink @jacobrossi or any other MS folks... any thoughts on this?

-- 
GitHub Notification of comment by patrickhlauke
Please view or discuss this issue at 
https://github.com/w3c/pointerevents/issues/152#issuecomment-259096549

 using your GitHub account

Received on Wednesday, 9 November 2016 00:19:53 UTC